graphql-spec
graphql-spec copied to clipboard
graphql
GraphQL is a query language and execution engine tied to any backend service.
### Preface The [Global Object Identification](https://graphql.org/learn/global-object-identification) introduces a "best practice" for a GraphQL server implementation. **The problem is that it is not very strict and it makes hard to write...
I'm looking to clarify whether it should be valid for a field to be resolved with both a value and an error in the global errors list. This scenario came...
As we explore the incremental delivery solution space it's useful to consider the following orthogonal axes independently: * Asynchronous versus synchronous data delivery * Lazy versus eager data resolution **This...
* Updates the `path` on the pending object to point to defer location. Only one pending payload will be sent per `path`. Clients can use this to determine if a...
As it currently stands, the “breaking change” GraphQL best practice is largely based upon the assumption that server schemas are never older than client schemas, which is not the case...
This attempts to clarify some naming conventions in the spec and makes one meaningful syntax change. This changes `SchemaDefinition` to have a zero-or-more list of `OperationTypeDefinition` rather than one-or-more. It...
I would like some clarification on using variables in scalars. Given the following schema: ```graphql scalar Custom type Query { hello(custom: Custom!): String! } ``` We know that the following...
GraphQL Mutation how to make fields optional to update fields only by selection and generate schema
I have a graphql mutation defined as follows ``` updateParts( partId: String! parts: PartRequest! ): UpdatePartsResponse! input PartRequest { name: String! image: Strings! boltTypes: [Bolts]! } input Bolts { code:...
Update: RFC PR is here! https://github.com/graphql/graphql-spec/pull/746 --- For example, given this schema: ```graphql type Business { reviews: [Reviews] name: String } type Review { body: String ... } ``` -...
I've heard live queries alluded to on various podcast episodes and in the RFC for subscriptions, but it's unclear to me whether there's a repository of ideas on what this...
