#35126: forms.NullBooleanField's validation logic is surprising
------------------------------+--------------------------------------
Reporter: Jeremy Lainé | Owner: Gaurav sah
Type: Bug | Status: closed
Component: Forms | Version: 5.0
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: assigned => closed
* resolution: => invalid
Comment:
It's clearly
[https://docs.djangoproject.com/en/5.0/ref/forms/fields/#nullbooleanfield
documented] with what kind of widgets (and set of choices) you can use
`NullBooleanField()`:
> ''"NullBooleanField may be used with widgets such as Select or
RadioSelect by providing the widget choices:"''
I don't see anything to fix here.
--
Ticket URL: <https://code.djangoproject.com/ticket/35126#comment:3>
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/0107018d1df70752-b033f1cf-628f-4af0-ac3c-6a4408067910-000000%40eu-central-1.amazonses.com.
