Changes between Initial Version and Version 1 of Ticket #29921, comment 1


Ignore:
Timestamp:
Nov 5, 2018, 4:58:18 PM (6 years ago)
Author:
Tim Graham

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #29921, comment 1

    initial v1  
    11This 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.
     2
     35fa4f40f45fcdbb7e48489ed3039a314b5c961d0 caused the change.
Back to Top