Add configurable OAuth scopes to Fast42 initialization#51
Merged
Conversation
Copilot created this pull request from a session on behalf of
FreekBes
June 4, 2026 20:45
View session
FreekBes
approved these changes
Jun 4, 2026
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
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.
Fast42 previously hardcoded OAuth scopes in
getAccessToken, preventing scope customization at initialization time. This change adds configurable scopes on initialization and preserves the existing default behavior (public,projects).Scope configuration in constructor
Fast42Settingsobject with optionalscopes?: string[].['public', 'projects'].Token request scope composition
scope=projects%20publicwith dynamic scope composition from settings.getAccessTokennow buildsscopeasthis._scopes.join('%20').Documentation and usage updates
scopesfield and default value.