graphql-spec
graphql-spec copied to clipboard
graphql
GraphQL is a query language and execution engine tied to any backend service.
This is a follow-up to #825 that proposes adding the `@oneOf` directive to object types (output objects). This is a draft right now as I've not yet had time to...
**Note: this is a very early thought-dump** Given the following schema and operation: ```graphql interface Searchable { id: ID! } type User implements Searchable { id: ID! name: String! }...
Often times we want to fetch just a single field from a nested relation. e.g. ``` { clients(limit: 5) { id programs { shortName } } } ``` It would...
As discussed in #232, `__id` doesn't really make sense if it actually returns the global ID, since double-underscore fields are usually used for type information. But what if it _did_...
An alternative proposal for the often requested (#476, #542) ability to distinguish optional inputs from nullable inputs. It doesn't propose any change to core GraphQL, just conventions and directives. It...
# RFC exporting variables between queries This RFC calls for the ability to "export" variables from one query into another. This allows a single server call to be made and...
**Problem** The spec, as it is currently, is ambiguous when defining how a union type should be handled when used to fulfill an interface. > An object field type is...
Pull request for https://github.com/graphql/graphql-spec/issues/943
When defining an enum with a Number String like `"11201"` or an Int like`11201`, it will result in a schema validation error `Names must match /^[_a-zA-Z][_a-zA-Z0-9]*$/ but "11201" does not.`...
We need to sync our models from server to client. So also need to convert them from JSON exactly. With GraphQL this is becoming very painful. Here's what we have...
