Closed owencompher closed 7 months ago
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 "None"
and the builtin None
. I'm not sure about the best way to do that so I'll leave it up to you
Thanks so much!
the Discord authentication url expects the prompt argument to be "consent" or "none", by default "consent". If set as
None
in the blueprint constructor, it remainsNone
until 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.