Make client_id optional #52
Closed
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
|
The device flow method seems to be aspirational still @hansmbakker is it? Just judging by your link in #51 It seems like it's not something that is available yet, am I wrong? It does seem like the PKCE method might be possible, and SHA encoding is probably requires device specific code, so maybe only available on ESP32 for example, but I'd imagine that satisfies the majority of users |
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.
PR for #51 - @witnessmenow this is still work in progress. I still need to remove code duplication in
requestAccessTokensDeviceFlowfor exampleAre you opiniated about code styling? I noticed the
prettierplugin formatted the code - if you have another formatting I should follow, please let me know.