#6652: Allow 'clean()' to specify the wrong field
---------------------------------------------------+------------------------
Reporter: Daniele Varrazzo <[EMAIL PROTECTED]> | Owner:
nobody
Status: closed | Component:
django.newforms
Version: SVN | Resolution:
wontfix
Keywords: feature | Stage:
Unreviewed
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
---------------------------------------------------+------------------------
Changes (by russellm):
* keywords: => feature
Comment:
Malcolm: Valid point about the ordering requirement, although I'm not
convinced that it is a problem in practice. The error message needs to be
tied to a specific field, and you can always set up the field order so
that the field with the error is last.
This enforces an order for presentation that may not be natural, but only
matters if you are rendering using form.as_*; if presentation order
doesn't match logical order, you can manually render each field.
My rejection of this idea was based on the fact that it introduces a
second way to raise field errors. However, I'm only a -0. Regardless,
better documentation of Form._errors is probably a good idea.
--
Ticket URL: <http://code.djangoproject.com/ticket/6652#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
