#26596: Document {{ csrf_input }} in Jinja2 templates
-------------------------------+-------------------------------------
Reporter: aaugustin | Owner: bjcubsfan
Type: Bug | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+-------------------------------------
Comment (by bjcubsfan):
Replying to [comment:6 aaugustin]:
> I believe this information would be more discoverable in the CSRF
reference documentation, either in the "How to use it" section or in a new
section.
>
> We should talk about:
> - the API offered by built-in template backends
> - requirements for third-party backends, as described in PEP 182
(basically they have to provide a solution, but that solution isn't
specified)
>
> This will likely require tweaking the content a bit to clarify that the
main examples are specific to Django templates.
I think you mean [https://github.com/django/deps/blob/master/final/0182
-multiple-template-engines.rst DEP 182].
--
Ticket URL: <https://code.djangoproject.com/ticket/26596#comment:16>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.76bbe33e28443e3bf353441d8ffee276%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
