Enhance device code documentation with semantics details #17
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.
Hello there 👋
I would like to add a foldable Details section documenting the lifecycle and constraints of device codes.
The goal is to clearly explain what is and is not possible once a device code has been issued and consumed, in particular:
This clarification would have been useful when investigating whether a new access token or refresh token could be obtained after the lifetime of the first refresh token ended, without forcing a new device authentication.
I believe this addition will help avoid incorrect assumptions and reduce future confusion around the device code flow.