Ticket #6705 [1] proposes that 'form.errors' be changed to somehow
provide a "prettier" display not based on the underlying field name
(which is currently used as the key in the errors dictionary).
The person who opened this ticket contends that it is a common issue,
and that there is no existing way to work around the desire to simply
do '{{ form.errors }}' in a ticket and have it display as he desires.
Personally I'm of the opinion that granular error output and
customizable error classes, though not precisely the solution asked
for in this ticket, provide adequate options at both ends of the
spectrum (granular output for fine-grained form display, custom error
classes for the simple case of printing a form), but the submitter has
repeatedly reopened the ticket and asked for broader consideration.
Since the submitter has not followed repeated advice/trout-slapping to
the effect that this list is a better discussion medium, I'm bringing
it up on his behalf.
Thoughts?
[1] http://code.djangoproject.com/ticket/6705
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
