Clarify: Adds more mentions of __ as reserved by introspection system.#244
Merged
Clarify: Adds more mentions of __ as reserved by introspection system.#244
__ as reserved by introspection system.#244Conversation
The spec chapter on introspection mentions that type artifacts must not be named with "__" since it is reserved. This clarification repeats this information closer to the spec on type system itself along with the rules for determining if object/interface types are valid.
Contributor
|
Does this exclude the possibility of using |
Collaborator
Author
|
Certainly if ids end up both using I'd hope we can avoid that outcome though. So if ids are not defined in the schema and are accessed as meta-fields, they should use |
This was referenced Jan 24, 2017
IvanGoncharov
pushed a commit
to IvanGoncharov/graphql
that referenced
this pull request
Jun 17, 2017
…em. (graphql#244) The spec chapter on introspection mentions that type artifacts must not be named with "__" since it is reserved. This clarification repeats this information closer to the spec on type system itself along with the rules for determining if object/interface types are valid.
saerdnaer
added a commit
to saerdnaer/graphql-tools
that referenced
this pull request
Apr 6, 2021
graphql "__fake" must not begin with "__", which is reserved by GraphQL introspection. c.f. graphql/graphql-spec#244
8 tasks
saerdnaer
added a commit
to saerdnaer/graphql-tools
that referenced
this pull request
Apr 6, 2021
graphql "__fake" must not begin with "__", which is reserved by GraphQL introspection. c.f. graphql/graphql-spec#244
yaacovCR
pushed a commit
to ardatan/graphql-tools
that referenced
this pull request
Apr 12, 2021
* fix error as __ is reserved for introspection graphql "__fake" must not begin with "__", which is reserved by GraphQL introspection. c.f. graphql/graphql-spec#244 * run yarn changset
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 spec chapter on introspection mentions that type artifacts must not be named with "__" since it is reserved. This clarification repeats this information closer to the spec on type system itself along with the rules for determining if object/interface types are valid.