#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 Jacob Walls):
Greetings, all. I think we need to take a step back. A form with every
subfield empty on an optional MVF should pass validation, and it does, and
there is a test in the suite for it. (The implication in the body of the
ticket is not quite right.) So I suggest the linked patch avoid making
changes to validation.
The reporter wanted the field to be required in reality but didn't want to
let `required=True` on the MVF because it made every subfield have the
HTML required attribute. I suggest renaming the ticket to focus on this
specific piece. I suggest we only handle what solves the reporter's use
case: when the MVF is `required` but `require_all_fields=False` set the
required attribute on the widget based on the subfield.
--
Ticket URL: <https://code.djangoproject.com/ticket/29205#comment:18>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.acda96583aecf5de2fd74c85f792e8bf%40djangoproject.com.
