graphql-spec
graphql-spec copied to clipboard
graphql
GraphQL is a query language and execution engine tied to any backend service.
Changed capitalization of subsections to first-cap style like in the rest of the doc
There are 38 occasions of phrase 'must not be' in the spec; this is the only one with such a strange capitalization
Explanation, current version: > Supporting subscriptions is a significant change for any GraphQL service. who is changing what? why we assume certain order of building GraphQL service - queries mutations...
Been suggested before but I'm adding another spin on it. Lot of people requesting and a lot of up-votes for, I see answers as to why it's not being implemented...
Motivation: IsSubType could be re-used within ResolveAbstractType when its behavior is clarified. See: #973.
add assertions from current behavior of reference implementation
It's common in the ecosystem to use `extensions` on a GraphQL request to share additional information with the server; for example Apollo Persisted Queries uses it to indicate the hash...
The explanatory text for algorithm had not been updated I guess when repeatable option was added for directives. This is a fix
Fix: exact type match is not required for implementing field; might be of covariant type
Complements #939 Addresses #711 Similar to #939, this PR expands the robustness of the type system by allowing types that actually fulfill interfaces to be recognized as such by the...