graphql-spec icon indicating copy to clipboard operation
graphql-spec copied to clipboard

GraphQL is a query language and execution engine tied to any backend service.

Results 202 graphql-spec issues
Sort by recently updated
recently updated
newest added

# Typed Scalars Some time before i started writing subset language of GQL (with name [iris](https://github.com/iris-qraphql/iris-js)) which would take best parts of GQL and simplify and generalize it. although it...

Default Root Op type names: removed duplicate statement, added that only Query type is required. @benjie argued previously that the second sentence (starting with Likewise...) is not a duplicate, it's...

@rivantsov Pointed out in #978 that there's some ambiguity around when the `schema` keyword can be omitted from the SDL. Upon careful reading I've noticed that there is additional ambiguity...

✏️ Editorial

Based on @leebyron suggestion in #203: > I’m happy to entertain a formal RFC to add errata to the spec to explain that .graphql is the preferred extension when saving...

The examples clearly show mutating fields (changeBirthday); since mutating fields are allowed only on top level, we clearly see the 'top' level of mutation request; however, there is no op...

[Directives Order Is Significant](https://spec.graphql.org/draft/#sec-Language.Directives.Directive-order-is-significant) sub-section is in section "2. Language", which talks about Query language. The directive order example surprisingly uses a type definition, while type system and its SDL...

Corresponding `graphql-js` pull request: https://github.com/graphql/graphql-js/pull/2319 Please keep discussion limited to specifics on how the spec text is written. There is a dedicated discussion forum for questions, feedback, and comments on...

📄 Draft (RFC 2)

The main point here is to remove 'when executed in PARALLEL'; service is free to execute the request 'normally' - in any order it wants, parallel or not. But I...

the current version mentions executor (what is that by the way?), and then: > this is covered in that section which section is not clear, we do not have 'executor'...