Top graphql-js issues

Restructuring of Type Definition API

needs exploration
leebyron picture leebyron·19 Aug 2015·2 Comments

Reducing executor

needs exploration
freiksenet picture freiksenet·6 Jul 2015·31 Comments
👍8

Provide example through tests for mutation queries.

hekike picture hekike·4 Jul 2015·4 Comments

Breaking change with deprecated fields not being included by default

question
Betree picture Betree·30 Oct 2020·12 Comments
👍1

Allow result type and variables type to be inferred from `DocumentNode`/`Source` using TypeScript type system

enhancement
dotansimha picture dotansimha·3 Aug 2020·3 Comments
👍2

Error: Must provide Source. Received: undefined after upgrade to [email protected]

Fi1osof picture Fi1osof·2 Apr 2020·18 Comments
👍17 👀5 👎4

parser: Improve error message for description followed by extension definition

enhancement
luandro picture luandro·23 Jan 2020·4 Comments

Allow schemaPrinter to be customized / extended.

enhancement
j picture j·8 Jul 2019·5 Comments
👍3

Design proper error names

enhancement
rogierschouten picture rogierschouten·3 May 2019·6 Comments
👍3

Large memory allocations and very slow execution when type errors occur in complex inputs

bug
SoyYoRafa picture SoyYoRafa·22 Feb 2019·5 Comments
 Previous issues
Next issues