#32429: Configurable "always available" InclusionNode context variables
-------------------------------------+-------------------------------------
Reporter: Michael Gisi | Owner: nobody
Type: New feature | Status: closed
Component: Template system | Version: 3.1
Severity: Normal | Resolution: wontfix
Keywords: context, inclusion | Triage Stage:
tag, template | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Michael Gisi):
Replying to [comment:1 Mariusz Felisiak]:
> Thanks for this ticket, however creating a new setting is always
controversial and we don't want tag-specific settings. The `csrf_token` is
a special case (see #12095) to make CSRF protection to be as simple as
possible. You can always subclass `InclusionNode` and add a custom
decorator.
>
> Feel-free to start a discussion on DevelopersMailingList if you don't
agree.
Understood - we will subclass `InclusionNode` to get the desired behavior.
Thanks for the quick response.
--
Ticket URL: <https://code.djangoproject.com/ticket/32429#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/062.fb86a06966b4966cbbed32bf4c18f725%40djangoproject.com.
