tickets: 1338

This data as json

id created changetime last_pulled_from_trac stage status component type severity version resolution summary description owner reporter keywords easy has_patch needs_better_patch needs_tests needs_docs ui_ux
1338 2006-02-10 05:47:06 2006-07-07 19:25:14 2022-03-06 03:23:05.053198 Unreviewed closed Generic views task trivial dev fixed Undefined context variables should not resolve to the value of TEMPLATE_STRING_IF_INVALID The new TEMPLATE_STRING_IF_INVALID is a useful setting but it seems to have some problems currently. With the current implementation undefined context variables are actually resolved to the value of TEMPLATE_STRING_IF_INVALID. This means that {% if some_undefined_variable %} can evaluate true. Also {{{FilterExpression}}} is passing the TEMPLATE_STRING_IF_INVALID value through the filters, which is probably not going to fit with user expectations. Perhaps {{{resolve_variable}}} should be consistently raising an exception for all unresolvable variables and {{{Node}}} renderers and {{{FilterExpression}}} should be returning TEMPLATE_STRING_IF_INVALID directly where appropriate. This would be slightly backwards incompatible for people using the guts of the template renderer in their template tags. russellm django@kieranholland.com   0 0 0 0 0 0