#28618: Add an easier way to make templates substitutions raise an exception on
error
-------------------------------------+-------------------------------------
Reporter: Facundo Batista | Owner: Ahmed
| Nassar
Type: New feature | Status: assigned
Component: Template system | Version: 1.11
Severity: Normal | Resolution:
Keywords: template error | Triage Stage: Accepted
substitution |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
The current PR is only adding an option to raise the VariableNotFound
exception, and only as a “global” flag on the template backend.
Given how prevalent the reliance on missing variables is (and missing
steps in variable chains) I’m not this will be at all usable. (There was
some discussion recently about allowing such opt-in to be per template,
for example. [https://forum.djangoproject.com/t/raise-error-for-missing-
variable-used-in-template/39776/9 forum thread] )
There’s nothing in the PR addressing Tim’s points from comment:6, which
was the basis for accepting.
--
Ticket URL: <https://code.djangoproject.com/ticket/28618#comment:13>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019616c3bcfa-a4aa6921-b3f5-4a32-95b9-63170a7b1355-000000%40eu-central-1.amazonses.com.
