Opened 5 years ago

Closed 5 years ago

Last modified 3 years ago

#11889 closed (fixed)

Order for context being override isn't clear for Context Processors and Views

Reported by: francis Owned by: nobody
Component: Documentation Version: 1.1
Severity: Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

The order at which the same key gets override in the context isn't clear from the current docs when the same key exist from the view and context processor.

Current behavior is the context processor will override view context with RequestContext(request, your_dict) (SmileyChris on IRC)

Change History (4)

comment:1 Changed 5 years ago by jacob

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 5 years ago by ubernostrum

  • Resolution set to fixed
  • Status changed from new to closed

(In [12669]) Fixed #11889: Documented the fact that context processors will overwrite pre-existing context variables of the same names.

comment:3 Changed 5 years ago by ubernostrum

(In [12670]) [1.1.X] Fixed #11889: Documented the fact that context processors will overwrite pre-existing context variables of the same names. Backport of [12669] from trunk.

comment:4 Changed 3 years ago by jacob

  • milestone 1.2 deleted

Milestone 1.2 deleted

Note: See TracTickets for help on using tickets.
Back to Top