[RFC] Make operation name optional. #99
Merged
Conversation
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
Based on feedback from those using GraphQL and inspired by RelayQL's syntax, this makes operation names optional. The primary value is the ability to express mutations (or eventually subscriptions) without being required to provide a name if the name adds no value for your use case. (Value typically being query disambiguation and logging). Systems which want to enforce a name for queries should have a separate linting/validation rule - such a rule would probably also want to ban "query shorthand"
|
I like it. Ship it. |
leebyron
added a commit
to graphql/graphql-js
that referenced
this pull request
Oct 1, 2015
leebyron
added a commit
that referenced
this pull request
Oct 1, 2015
[RFC] Make operation name optional.
leebyron
added a commit
to graphql/graphql-js
that referenced
this pull request
Oct 1, 2015
swolchok
added a commit
to graphql/libgraphqlparser
that referenced
this pull request
Oct 1, 2015
jhgg
added a commit
to graphql-python/graphql-core-legacy
that referenced
this pull request
Oct 6, 2015
Implements graphql/graphql-spec#99 Closes #6
sogko
added a commit
to sogko/graphql
that referenced
this pull request
Mar 8, 2016
Parents: 2cfbfcec58 Author: Lee Byron <lee@leebyron.com> Date: 2 October 2015 at 6:37:42 AM SGT Commit Date: 2 October 2015 at 6:44:20 AM SGT [RFC] Make operation name optional. Implements graphql/graphql-spec#99
6 tasks
mattstern31
pushed a commit
to mattstern31/graphql-gqllero-repository
that referenced
this pull request
Nov 10, 2022
Parents: 2cfbfcec58 Author: Lee Byron <lee@leebyron.com> Date: 2 October 2015 at 6:37:42 AM SGT Commit Date: 2 October 2015 at 6:44:20 AM SGT [RFC] Make operation name optional. Implements graphql/graphql-spec#99
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.
Based on feedback from those using GraphQL and inspired by RelayQL's syntax, this makes operation names optional.
The primary value is the ability to express mutations (or eventually subscriptions) without being required to provide a name if the name adds no value for your use case. (Value typically being query disambiguation and logging). Systems which want to enforce a name for queries should have a separate linting/validation rule - such a rule would probably also want to ban "query shorthand"