Declare DeployTargetConfig related api fields as unstable #2877
Conversation
This file contains 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.
Checklist
The GraphQL spec includes an
@deprecateddirective. All the dev tools I've tried are aware of this directive and will surface it in an explicit way. I think this would be a nicer way to warn users that the API is unstable.Cons: it's maybe not correct to call it "deprecated" instead of unstable/alpha, but then all the dev tools wouldn't show that info.
Examples from dev tools:
Insomnia.app
GraphiQL
GraphQL Playground
Closing issues
n/a