#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 Sarah Boyce):
I think #12627 covers your previous comment about `readonly_fields` in the
admin.
Replying to [comment:4 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).
If you want to discuss changing the design, you should propose this in the
[https://forum.djangoproject.com/c/internals/5 Django forum] and see if
you can get agreement from the community for this change. As this would
impact a lot of existing projects, we need strong community agreement
after which we can accept a ticket 🙂
--
Ticket URL: <https://code.djangoproject.com/ticket/35367#comment:5>
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/0107018ec887f30b-ab71b99e-b49e-4cbf-9c87-111dfe574c35-000000%40eu-central-1.amazonses.com.
