On 7/26/06, Guillaume Pratte <[EMAIL PROTECTED]> wrote: > To verify the variables before passing control to the template system is not a > viable solution, and would break the DRY principle (Don't Repeate Yourself). > I would have to know what variables are defined in my templates in my code > calling the template, thus duplicating the information and rendering my code > harder to maintain.
Nevertheless, there's no easy way to mediate between "DRY as ironclad rule" and "don't let a bad variable name break your whole site". Django tends to err on the side of "don't break the site", even when that means a little more work. For your case, you might want to take a look at the TEMPLATE_STRING_IF_INVALID setting, which lets you specify a string to be inserted for invalid variables; running any sort of text search utility (such as grep) over your output file looking for that string will tell you immediately if something went wrong. Also, for a more general audience: take note that adding a ReST-formatted docstring to a view function will get it to display nicely in the admin documentation for the view, which is an extremely easy way of both documenting your code for programmers and letting your designers know which variables will be available in templates. For examples, look at the docstrings of any of the built-in generic views; they provide full listings of the context variables the views define. -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
