Re-implementation of Device Code Flow Integration in Vapor OAuth #24
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
This was referenced Jan 31, 2024
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.
I am re-submitting the integration of Device Code Flow into Vapor OAuth, as a fresh pull request following issues encountered with the previous PR #17 . This PR contains the same set of changes and updates that were intended in the original submission.
Key Aspects:
Reason for New PR:
The decision to create a new PR was due to complications with the original one, including review challenges. This fresh PR will help in maintaining a cleaner and more organized code history.
Please refrain from merging this PR until I have given the explicit go-ahead. I will update this thread and provide a clear notification once it is ready for final review and merging.