fix Discord prompt parameter #433
Merged
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
|
Great! Could you please add a test to cover these cases? (Both "none" and "consent" should be tested.) |
|
I would consider tweaking the docs to remove the ambiguity between the string |
|
Thanks so much! |
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.
the Discord authentication url expects the prompt argument to be "consent" or "none", by default "consent". If set as
Nonein the blueprint constructor, it remainsNoneuntil it is passed to the url, where it is left off entirely. Changing it to"none"fixes the issue without the possibility of breaking any other providers.It looks like this is the only provider with this kind of issue.