#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: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+---------------------------------------
Comment (by Carlton Gibson):
Hi David, good work.
I'll hazard an opinion.
Required **should** work at two levels, rather than overriding from the
parent.
Required on the MWF should mean "Can this set of sub-fields be skipped
entirely?".
Assuming No to that, i.e. that the MWF is required, then the individual
fields should respect their own required attributes.
I imagine a Date + Time MWF where the Time is optional. (🤷♀️)
In the limit, a required MWF with all optional sub-fields would be
required in name only.
That would be my first stab at the correct behaviour. It would be
interesting to see what the existing tests say about that.
--
Ticket URL: <https://code.djangoproject.com/ticket/29205#comment:13>
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.0ba2be1a53f12e2be23cc5adfd135891%40djangoproject.com.
