#23129: NullBooleanField to accept lower-case string representations of booleans
-----------------------------+------------------------------------
Reporter: wlonk | Owner: dhoffman
Type: New feature | Status: closed
Component: Forms | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-----------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"17e75d03f92cff7d1d5d4679a8a09b13e08f3264"]:
{{{
#!CommitTicketReference repository=""
revision="17e75d03f92cff7d1d5d4679a8a09b13e08f3264"
Fixed #23129 -- Added 'true' and 'false' to `NullBooleanField`.
JavaScript serializations of forms will sometimes render the boolean
values as the strings 'true' and 'false', in lower case. Rather than
repeat boilerplate in the JavaScript to circumvent this, it seems
reasonable to allow Django to understand the lower-case versions of the
booleans.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/23129#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.25f3c02ec7a8b307f4ac830544487f95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
