graphql-spec
graphql-spec copied to clipboard
graphql
GraphQL is a query language and execution engine tied to any backend service.
Supersedes https://github.com/graphql/graphql-spec/pull/1036 See also https://github.com/graphql/graphql-wg/pull/1401 for the glossary. This PR is a draft of what spec edits might look like to give a more precise idea of what it could...
This PR builds on #1065. This introduces a directive on operations that disables the null/error propagation behavior by treating all Non-Null types as if they were Semantic-Non-Null types (see #1065)....
I know that the spec is agnostic regarding serialization formats, but I felt the need to share this idea with future readers, since it relates to the JSON format. Sometimes...
The spec claims: | Expected Type | Provided Value | Coerced Value | | ------------- | ---------------- | --------------------------- | | `[Int]` | `[1, 2, 3]` | `[1, 2, 3]`...
Currently this query which would fail validation due to the [All Variable Usages Are Allowed rule](https://spec.graphql.org/draft/#sec-All-Variable-Usages-Are-Allowed)'s explicit validation steps: ```gql type Query { dummy (arg: [String]): String } query ($arg:...
# Problem Take as a motivating example: ```graphql type Query { animals: [Animal] } interface Animal { name: String } type Dog implements Animal { name: String } type Baiji...
@stream and @defer are collaborative efforts between the client and server to improve the application’s time-to-interact metric. This issue discusses some important reasons to enable the server to choose whether...
As we dive into full schemas, introspection and more (see https://github.com/graphql/graphql-spec/pull/1036), I'd find it useful to have an authoritative source for built-in definitions that come with a GraphQL implementation (scalar,...
"should" seems too strong here given a schema can have a description and directives applied to it.
