graphql-spec
graphql-spec copied to clipboard
graphql
GraphQL is a query language and execution engine tied to any backend service.
### Background This is a very initial idea for allowing a shorthand for using/matching variables and arguments on a selection set. In many projects we (The Guild) worked with, we...
I like the concept of GraphQL, but I'm really surprised by the ASCII-limitation in the spec. Many years ago, that limitation made sense, but today it sounds like a blast...
**THIS RFC HAS BEEN SUPERSEDED** by `@oneof`, for now at least... See: https://github.com/graphql/graphql-spec/pull/825 --- This is an RFC for a new "Tagged type" to be added to GraphQL. It replaces...
See http://spec.graphql.org/October2021/#sec-Descriptions : > To allow GraphQL service designers to easily publish documentation alongside the capabilities of a GraphQL service, GraphQL descriptions are defined using the Markdown syntax (as specified...
Custom directives have been widely used to increase the power of GraphQL, however they are missing from object field names. _NOTE: Such directives are also missing from argument names as...
This addresses #410 *Directives at the top of a SDL file* # WIP :heavy_check_mark: Required grammar and introspection changes included
In some of our tool, we need to be able to pass an arbitrary value as an argument of a directive, i.e. value which can be anything and can’t be...
This is a **proposal** to bring Relay-style [Fragment Arguments](https://www.internalfb.com/intern/staticdocs/relay/docs/api-reference/graphql-and-directives/#arguments) into the Spec as an **optional**, **client-only** language feature. # Overview We would allow clients to write GraphQL like: ``` query...
Following on from #776 and based on the [discussion in the GraphQL.js pull request](https://github.com/graphql/graphql-js/pull/2861#discussion_r619789288) I'm still uncomfortable with the single root field validation rule for subscription operations. Currently the "single...