-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrading to DRF 3.10.0 breaks settings #410
Comments
It seems someone is already on this issue. See PR |
I don't think changing the setting is enough. |
We cannot fix the incompatibility yet because another dependency, drf-yasg does not support drf 3.10 yet. axnsan12/drf-yasg#410 https://pulp.plan.io/issues/5125 re pulp#5125
We cannot fix the incompatibility yet because another dependency, drf-yasg does not support drf 3.10 yet. axnsan12/drf-yasg#410 https://pulp.plan.io/issues/5125 re #5125
I would love to read a statement from @axnsan12 regarding DRF's switch to OpenAPI (https://www.django-rest-framework.org/community/3.10-announcement/). Will it make sense to continue YASG? Should we refactor it to reuse more OOB features? Will it cease to exist by integrating its exclusive features to DRF? However, thank you for this amazing project. |
After upgrading to DRF == 3.10.0 following error message appears when trying to run server
Apparently,
SchemaGenerator
has been renamed toBaseSchemaGenerator
, with some changes.Adding the following lines to SWAGGER_SETTINGS in settings.py seems to work.
The text was updated successfully, but these errors were encountered: