Code

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#15276 closed (invalid)

More configurable unresolved template variables handling

Reported by: zimnyx Owned by: nobody
Component: Template system Version: master
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

So far there is one solution to debug unresolved template errors: settings.TEMPLATE_STRING_IF_INVALID. It doesn't offer to much control over what happens when such error occurs. Main motivation for creating this ticket was lack of possibility to track template var errors on production (TEMPLATE_STRING_IF_INVALID=).

My proposition to overcome mentioned limitation is to allow three levels of template error handling:

  • IGNORE (current default)
  • WARNING: possibility to track errors in production mode (when TEMPLATE_STRING_IF_INVALID=)
  • EXCEPTION: easily find errors when debugging

How about this?

Attachments (0)

Change History (2)

comment:1 Changed 3 years ago by anonymous

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to invalid
  • Status changed from new to closed

Trac isn't the right place to kick around vague ideas. It's a place to report a specific problem, or a specific solution.

If you want to have a design discussion, start a thread on django-dev.

comment:2 Changed 3 years ago by russellm

That last comment was me. Trac logged me out again...

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.