feat: declare setup.oauth on the react-oauth manifest#5
Merged
Conversation
Signals the CLI to run OAuth provider prompts and wire the chosen providers into the scaffolded auth server when this template is selected.
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.
Adds
setup.oauth: trueto the react-oauth template manifest. This signals the Seamless CLI to run its OAuth provider prompts (pick Google/GitHub/Microsoft/GitLab, paste client id + secret) and wire them into the scaffolded auth server when this template is selected.Pairs with the seamless-cli change that reads this flag. Older CLIs ignore the field, so the template still scaffolds as before for them (graceful degradation).