#29921: Default BooleanField.required different from Django 2.0 when using
choices
-------------------------------------+-------------------------------------
Reporter: bogdanbatog | Owner: nobody
Type: Bug | Status: new
Component: Forms | Version: 2.1
Severity: Normal | Resolution:
Keywords: BooleanField, | Triage Stage:
widget, required | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 1
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* type: Uncategorized => Bug
Comment:
This looks like expected behavior to me. With the model you gave, a true
or false value is required since the field can't be null, therefore the
user must provide a value. I imagine your use case might be an API request
where if the user didn't provide a value, a value of false was saved?
Django doesn't normally fallback to a model field default if a value isn't
provided to a form, but maybe this merits a mention in the release notes.
--
Ticket URL: <https://code.djangoproject.com/ticket/29921#comment:1>
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/069.549ee5b54a30af74b26e36652f52c845%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
