djoser.readthedocs.io not up-to-date
See original GitHub issue“Latest” documentation on djoser.readthedocs.io is not 1.3.0, but some different version. Specifically, SERIALIZERS.current_user
is missing from the settings documentation.
Compare: Outdated documentation on readthedocs Should-be documentation on github (CTRL-F “current_user”)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Welcome to djoser's documentation! — djoser 2.0.1 ...
Welcome to djoser's documentation!¶ · Available endpoints · Supported authentication backends · Supported Python versions · Supported Django versions · Supported ...
Read more >Migration Guide — djoser 1.1.5 documentation
The JWT Refresh endpoint requires the refresh token and returns a new access token. The JWT Verify endpoint no longer returns token ....
Read more >Migration Guide — djoser 1.1.5 documentation
Migrating from 1.1 to 1.2¶. There is no urgent need to change anything as backward compatibility is retained. That being said we ask...
Read more >Release 2.0.1 Piotr Szpetkowski - djoser's documentation!
REST implementation of Django authentication system. djoser library provides a set of Django Rest Framework.
Read more >Release 1.1.5 Piotr Szpetkowski - djoser's documentation!
REST implementation of Django authentication system. djoser library provides a set of Django Rest Framework.
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
I’m on it. We needed to regain the access to readthedocs from previous dev.
I was able to migrate from 1.3.2 to 1.4.0 (and from rest_framework_jwt to rest_framework_simplejwt), but it wasn’t a pleasant couple of hours. My notes for the documentation, so as to save anyone else pain.
Authorization: JWT <token>
The rest_framework_simplejwt expects headers like:
Authorization: Bearer <token>
Does that mean a rewrite of the code using your API ? Not necessarily; put something like this in your settings.py file
I hope this information is of use for the document writers. Cheers.