Clarify documentation regarding setup #130
Open
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
There is some confusion caused by the AUTHENTICATION_BACKENDS setup instructions from the documentation, which when not set properly, it will cause confusing errors to appear which are not related to the error source. Example of such confusion: - PedroBern#126
|
@PedroBern how does merging a MR work for this repo? Should I add somebody as the reviewer and/or assignee? It seems I can't do this myself though. Given the number of open issues and pending PRs (some from March/April 2020, an important question arises: is this repo abandoned and not maintained anymore? |
To keep it short, yes, sort of. There are several Graphene & Django related tools which not officially abandoned but also not getting maintained anymore. I think this is one of them. |
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.
There is some confusion caused by the AUTHENTICATION_BACKENDS setup instructions from the documentation, which when not set properly, it will cause confusing errors to appear which are not related to the error source.
Example of such confusion: