graphql-spec
graphql-spec copied to clipboard
graphql
GraphQL is a query language and execution engine tied to any backend service.
Use case: inquiring about specific directives such as `@defer` and `@stream`
Hi! I think this may be a spec bug. Say I have an interface with no implementers. ```graphql interface Intf { field: Int } type Query { intf: Intf }...
## **GraphQL Document-Level Directives Proposal** ### **Introduction** As GraphQL's popularity continues to surge, its potential extends beyond just efficient data fetching. Solutions like Apollo Federation, Hasura, Prisma and Tailcall have...
This PR builds upon @IvanGoncharov's [2021 RFC](https://github.com/graphql/graphql-spec/pull/892), with changes rebased onto the current spec and updated to incorporate feedback from previous discussion as well as an additional editorial pass. Descriptions...
This is a rewrite of - #1153 It is re-implemented on top of the recent editorial work (e.g. renaming `_field error_` to `_execution error_`) and also makes a significant change...
Hey. Currently, [per spec, paragraph 5.3.2](https://spec.graphql.org/draft/#sec-Field-Selection-Merging), two fields of the same name cannot be selected on two different, mutually exclusive types, if field types or arguments differ. E.g. given this...
Extracted from the full PR (https://github.com/graphql/graphql-spec/pull/1110) and targeting an integration branch to aid in review. Helpful reference material: * Response format examples: https://github.com/graphql/defer-stream-wg/discussions/69 * GraphQL Conf talk: https://www.youtube.com/watch?v=LEyDeNoobT0
Currently the spec doesn’t say much about schema evolution ([this short paragraph](https://spec.graphql.org/draft/#sec-Validation.Type-System-Evolution)). Would it make sense to have it cover this topic more extensively? For instance, an exhaustive enumeration of...
Extension to #1039 Currently: ``` type GroupedFieldSet = Map ``` I propose that we defined "field set" to be an ordered set (rather than list) of fields that all share...
This is essentially solution 8 to the [Semantic Nullability RFC](https://github.com/graphql/graphql-wg/blob/main/rfcs/SemanticNullability.md): - Enables **semantic nullability** to be reflected in schemas without breaking legacy behavior. - Facilitates **incremental adoption** of modern error...