#22105: Model error messages overwritten by modelform django defaults
-------------------------------------+-------------------------------------
Reporter: daniel@… | Owner: Dr_White
Type: Bug | Status: closed
Component: Forms | Version: master
Severity: Normal | Resolution: invalid
Keywords: error_messages, | Triage Stage:
model, error, form, | Unreviewed
_update_errors | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by MikeA):
* status: new => closed
* needs_better_patch: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_docs: => 0
Comment:
This behaviour is deliberate.
MyModelForm's error messages are more specific than MyModel's, i.e. form
error messages overriding behaviour gives us the way to customize a
model's error messages.
This might make more sense when we note that multiple forms can be used
with one Model subclass, but not really the other way around.
--
Ticket URL: <https://code.djangoproject.com/ticket/22105#comment:1>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/079.a96952a2caf1a16a5fa95973edaa8d29%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
