Changes between Version 1 and Version 2 of Ticket #28618, comment 13
- Timestamp:
- Apr 8, 2025, 1:59:08 PM (5 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28618, comment 13
v1 v2 1 1 The [https://github.com/django/django/pull/19353 current PR] is only adding an option to raise the VariableNotFound exception, and only as a “global” flag on the template backend. 2 2 3 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] )3 Given how prevalent the reliance on missing variables is (and missing steps in variable chains) I’m not convinced 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] ) 4 4 5 5 There’s nothing in the PR addressing Tim’s points from comment:6, which was the basis for accepting.