-
Notifications
You must be signed in to change notification settings - Fork 270
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
Getting bug when generating schema, possible reason dj_rest_auth version 3.0.0 release leads to breaking changes #937
Comments
Ahh, I see. They cleaned up their awkward setup in favor of something more idiomatic for DRF. nice! will have a fix soon. |
thanks for your quick help, @tfranzel! |
fix dj-rest-auth>=3.0.0 breaking changes #937
Thanks for this @tfranzel |
yes. I'll want to look at another issue first but I plan in the next couple of days. |
@tfranzel I don't want to push you, but are you able to estimate when this fix will be released? Thank you! |
no worries. there were a couple of issues raised. currently working on a long pending feature. took longer than anticipated. end of week at the latest. |
closed with release |
When I try to create a schema via the command
python manage.py spectacular --file schema.yml
I get the following error message:ImportError: cannot import name 'JWTSerializer' from 'dj_rest_auth.app_settings'
I am using
dj_rest_auth==3.0.0
, which was released three days ago. I compared thedj_rest_auth.app_settings.py
file of version 3.0.0 with the latest major version before that (version 2.2.8) and if I am not mistaken,JWTSerializer
was indeed renamed toJWT_Serializer
in the 3.0.0 version. So it seems to me that this variable name change indj_rest_auth
is causing an bug indrf-spectacular
If my assumption regarding the cause for the bug is correct, could you please fix it?
The text was updated successfully, but these errors were encountered: