#13693: error_messages for fields in Model don't carry over to ModelForm
---------------------------------+------------------------------------------
Reporter: Aleks | Owner: anonymous
Status: closed | Milestone:
Component: Forms | Version: 1.2
Resolution: wontfix | Keywords: error_messages, forms, models
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------+------------------------------------------
Comment (by carljm):
> Marking this as wontfix since I don't believe this is an issue.
Honza, you certainly know a lot more than I do about model-validation, but
I don't think I agree with the wontfix here. In general my mental model of
ModelForms is that they pull as much information as possible from the
model definition for the form default, to minimize the boilerplate needed
to make a form for that model. Personally, I'd be surprised if I defined a
custom validation error message on a model field and found that it didn't
propagate to the ModelForm by default. It's possible that I'm missing
something important, but I can't think of a case where I wouldn't want
that as the default behavior. Maybe you can explain in a bit more detail
why that's a bad idea? Or else reopen, and I'm willing to put in some time
to work out the test-suite issues and any other problems with the patch.
--
Ticket URL: <http://code.djangoproject.com/ticket/13693#comment:3>
Django <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 django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
