Add support for DRF >= 3.14.0
See original GitHub issueNullBooleanField
was removed in DRF 3.14.0
which affect drf-spectacular
( see PR ). The latest drf-spectacular,
or any previous releases for that matter are incompatible with DRF>=3.14.0
. More specifically, drf-spectacular
should stop using NullBooleanField
as it’s been deprecated in DRF>=3.14.0
and start using BooleanField
with allow_null=True
.
I’m unaware wether there are further incompatibility issues with DRF >= 3.14.0 besides NullBooleanField
.
Issue Analytics
- State:
- Created 10 months ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Release Notes - Django REST framework
3.14.0. Date: 22nd September 2022. Django 2.2 is no longer supported. ... See the schema docs; Add support for Django 3.1's database-agnositic JSONField...
Read more >Compatibility issues with djangorestframework==3.14.0 #810
This breaks compatibility with drf-yasg 1.21.3. Description. With version 3.14.0, rest_framework.serializers.NullBooleanField was removed. Is ...
Read more >Changelog — drf-spectacular documentation - Read the Docs
NullBooleanField comment and add 3.14.0 to test suite #818 ... Add support for djangorestframework-dataclasses [Oxan van Leeuwen]. add version to schema for ...
Read more >djangorestframework - PyPI
Let's take a look at a quick example of using REST framework to build a simple model-backed API for accessing users and groups....
Read more >AttributeError: module 'rest_framework.serializers' has no ...
The support for NullBooleanField was removed in 3.14.0. I have raised an issue on the drf-yasg github asking for support for this version...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
also there was some issue with stale local
poetry
caches, which they fixed in newer versions i think. This led to not evenZ
updates being used.Got it! Appreciate the quick response. Keep up the good work 😄