Bunch of improvements on authentication documentation #1420
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kludex
approved these changes
Jan 18, 2022
I recommend a GitHub discussion or introducing the idea on our Gitter server. Thanks for the PR! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
AuthenticationBackend.authenticatesignature was updated here to handle both HTTP and websocket protocols, but the documentation still usesrequest.Also removing
UnauthenticatedUserimport inAuthenticationBackendexample, as it is not used, and adding some missing imports in a few examples.Side-note: The documention mixes single and double quotes usage for strings. Should a consistent style be used? Maybe https://github.com/asottile/blacken-docs could be helpful?