graphql-js
graphql-js copied to clipboard
graphql
A reference implementation of GraphQL for JavaScript
# Questions regarding how to use GraphQL We want to keep signal strong in the GitHub issue tracker – to make sure that it remains the best place to track...
I wasn't sure whether or not to make a new issue or comment on https://github.com/graphql/graphql-js/issues/594 but that one is so old I figured it would be preferable to start anew...
Also deprecated `ValidationContext.reportError` in favor of new `report` function with named argument. Motivation: subclassing allows you to distinguish between errors produced by `graphql-js`. Idea is to subclass all errors into...
...to try to avoid involuntary context switches. This seems to me to be pretty TETAW ("too easy to actually work").
Motivation: 1. Some visit context information is rarely used, this could be pathway toward refactoring, future-proofing any breaking changes to come. (see: https://github.com/graphql/graphql-js/issues/3225) 2. Eventually, BREAK and/or other visit controllers...
`extendSchema()` doesn't set `GraphQLSchema.description` if the `schema` definition is in the input `GraphQLSchema` instead of the AST. **Example** Running this code: ```typescript import { buildSchema, extendSchema, parse } from "graphql";...
Implements https://github.com/graphql/graphql-spec/pull/892
See https://github.com/ardatan/graphql-tools/issues/1453