graphql-spec
graphql-spec copied to clipboard
graphql
GraphQL is a query language and execution engine tied to any backend service.
This PR aims to improve the last minute changes to https://github.com/graphql/graphql-spec/pull/775 by improving the readability of the paragraph. The text `This modified type may recursively be a modified type` is...
**Problem**: There are a few issues one runs into when using the introspection of a schema to get the return types of fields. - nested query required for each NonNull...
Sometimes, product code might only be interested in the existence of an object. Currently, this forces a workaround of either querying `__typename` or adding a bool field like `has_thing`. It...
This change would make the root `query` operation type optional, consistent with `mutation` and `subscription`. In this proposal, schema introspection would still work as before, by allowing a "default" `query`...
This is the minimum viable edit to enable this feature. I imagine we'd also want to allow directive extensions if this feature is approved. #566
As @leebyron suggested during last WG I'm adopting #326 and rebasing it on top of current master. Currently, Custom Scalars only describe their name and no other behavior about them...
This is a follow-up to discussion in https://github.com/graphql/graphql-relay-js/issues/20#issuecomment-416809871. The current coercion rules, for convenience, allow passing in singular literals in positions expecting lists. However, they do not allow passing in...
# TL;DR: This RFC proposes adding the `why` field to GraphQL errors that contain a list of reasons why this error happened. ## Problem Statement Sometimes, during execution multiple errors...
This is a new attempt to add a date/time scalar to GraphQL in order to represent date and time. There has been previous discussions, which resulted in the decision not...
Based on this: https://github.com/graphql/graphql-js/issues/937#issuecomment-432857507 Currently we can't represent an empty object type: ```graphql type Mutation { createUser(email: String!, password: String!): CreateUserPayload! } type UserWithEmailAlreadyExists type WeakPassword type AuthPayload { user:...
