Permit mixed casing of string values for BooleanField validation #8970
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In this PR, all values of type
str
being serialized tobool
for fields typedBooleanField
are first cast to lowercase and then validated against the lists ofTRUE_VALUES
,FALSE_VALUES
, andNULL_VALUES
. Discovered this restriction when a user tried to send "Yes" as a valid value for a Boolean field to my team's Public-facing API.