#6907: Rethink the silent eating of exceptions in templates
-------------------------------------+-------------------------------------
Reporter: miohtama | Owner: nobody
Type: New feature | Status: closed
Component: Template system | Version: master
Severity: Normal | Resolution: fixed
Keywords: exception template | Triage Stage: Accepted
silent failure |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Christian González):
Does this ticket also apply to variables that are not found (because e.g.
misspelled)?
When I write
{{{
{{ nonexisting_variable }}
}}}
in a template; nothing happens, Django happily renders the page without
telling me that there is a wrong variable in a template.
Also,
{{{
{% for counter in existing_variable %}
<div>{{ counters }}</div>
{% endfor %}
}}}
shows nothing, no error and no output (mind the wrong 's' after counter) -
so variables declared IN the template are not checked neither.
Is there a chance that this is getting improved?
--
Ticket URL: <https://code.djangoproject.com/ticket/6907#comment:8>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.06800ffb38864f7e95fa63737c141ad3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
