Closed Bug 1204666 Opened 9 years ago Closed 7 years ago

switch from jinja2.Undefined to jinja2.StrictUndefined

Categories

(Input Graveyard :: Code Quality, defect)

Product:
Input Graveyard
Component:
Code Quality
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: willkg, Unassigned)

References

Details

(Whiteboard: p= s=input.2015q4) 

We're currently using jinja2.Undefined for when variables in the templates are undefined. This prints the empty string. Because of that, we never notice when we're using variables that aren't defined in the context in the templates. Ugh.

This bug covers switching to jinja2.StrictUndefined which raises exceptions when you try to use a variable not defined in the context. This will likely unveil a gazillion errors--we should fix those, too.
Whiteboard: p= s=input.2015q3
Making it clear we can't work on this until we finish up the Django 1.8 upgrade and switch to django-jinja.
Depends on: 1146686, 1167194
New quarter!
Whiteboard: p= s=input.2015q3 → p= s=input.2015q4
The Input service has been decommissioned (see bug 1315316) and has been replaced by a redirect to an external vendor (SurveyGizmo). I'm bulk WONTFIXing Input bugs that do not appear to be relevant anymore.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.