Personally, I prefer fireworks when a variable is not set.
Here's yet another possibility, just a variant on current code:
TEMPLATE_STRING_IF_INVALID = "<span class='template-var-error'>%
(expression)s: %(error)s</span>"
The above would be filled in by _resolve_lookup with appropriate
values.
Then you have a style:
template-var-error {
display:none; /* or inline or block */
color: red;
background-color: yellow;
border: solid 1px red;
}
This will display a nice error message for normal string use, but blow
up the template in places where a URL was expected.
E.g., <form action="<span class='template-var-error'>%(expression)s: %
(error)s</span>"> will probably fail in a fairly obvious way.
Just a thought.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@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-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
