Remove usage of depreciated NullBooleanField for drf 3.14.0 #65
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.
There is a new drf release https://www.django-rest-framework.org/community/release-notes/#3140
Here
NullBooleanField
is no longer available and so I removed the one reference to allow support for drf 3.14.0It was also not required as the
isinstance(field, BooleanField)
would return true for aNullBooleanFIeld
due to object inheritance:So I think we should be good 馃憤
Thank you for the package 鉂わ笍 @FlipperPA