Correct GraphQL CLI Prompt#15205
Merged
brandonkelly merged 2 commits into4.xfrom Jun 14, 2024
Merged
Conversation
Contributor
Author
|
This naming issue is actually present in 4.x as well—not sure how to target both branches… |
brandonkelly
force-pushed
the
bugfix/graphql-cli-prompt
branch
from
c3ee9b3 to
7d50310
Compare
[ci skip]
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
2 participants
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.
The
graphql/create-tokenaction prompts the user for a "Schema name", but it’s actually asking for a name for the new token! 😅