#35367: Multi-field constraint are not correctly handled when a form has one
field
marked as read-only
------------------------+--------------------------------------
Reporter: David | Owner: nobody
Type: Bug | Status: closed
Component: Forms | Version: 4.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------+--------------------------------------
Comment (by David):
Maybe an other way to express what I belive is: if there is any constraint
which involves more than one field it is not correct to allow excluding a
subset of those fields from validation while keeping the others in the
validation workflow.
With the provided code sample the validation of `field_1` **cannot** be
done without `field_2` (and vice-versa).
--
Ticket URL: <https://code.djangoproject.com/ticket/35367#comment:4>
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/0107018ec826e4b4-105bb62c-b5e2-43fe-9190-160753ea20b2-000000%40eu-central-1.amazonses.com.
