fix(migrate): normalize legacy OAuth scope - #392
Open
natalie-o-perret wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
@danielgtaylor wdyt? |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
scopeparameter accepted by v1 to v2's canonicalscopesparameter during legacy config conversionContext
Restish v1 accepted
scopeas an OAuth endpoint pass-through even though its documented parameter wasscopes. The v2 CLI can still tolerate that key as a pass-through, but embedders reading converted profiles use the canonicalscopesparameter and otherwise receive an empty scope.When both keys exist, the singular
scopevalue wins during conversion. This preserves v1 behavior, where endpoint pass-through parameters were applied after the value derived fromscopes.Fixes #393
Note
AI assistance: test coverage, PR description.