feat: generate OAuth2 Scopes and Descriptions variables #1470
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.
This change is underpinned by a new
ScopeDescriptions
map on theSecurity
struct that contains a mapping ofscope => scopeDescription
.We leverage this in three areas:
type ScopeName = string
alias.ScopeName
alias, we iterate over all Scopes and create consts for each Scope (with its corresponding scope string) and create a Map containing a mapping ofScopeName => ScopeDescription
.oauth2Scopes
Map to includeScopeName
aliased Scopes, rather than raw strings.