#29205: MultiValueField ignores a required value of a sub field
--------------------------------+---------------------------------------
Reporter: Takayuki Hirai | Owner: David Smith
Type: Bug | Status: assigned
Component: Forms | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------+---------------------------------------
Comment (by plidauer):
Hi all, I agree with Jacob. This doesn't seem to be an issue about whether
a MVF is semantically valid or required - it's about a specific behavior
which we can't currently achieve, at least not while using MVF.
The docs state:
When [require_all_fields] set to False, the Field.required attribute can
be set to False for individual fields to make them optional. If no value
is supplied for a required field, an incomplete validation error will be
raised.
But setting {{{required=True}}} on MVF level ignores the {{{required}}}
attribute on subfields regarding the HTML attribute which in turn comes
from the widget attrs.
--
Ticket URL: <https://code.djangoproject.com/ticket/29205#comment:19>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.49c55f913f55188ada1acbd6bff5c681%40djangoproject.com.
