Skip to content

Releases: graphql/graphql-js

v0.4.10

27 Oct 02:34
Compare
Choose a tag to compare

New:

  • buildClientSchema() now supports deprecated fields #216
  • Custom directives now supported by GraphQLSchema #215
  • concatAST() utility added, which helps support validation of graphql fragments spread across multiple sources (3a6b4d1)

Fixes:

  • Nested input objects with similarly named keys could falsely fail validation #206

v0.4.9

22 Oct 05:53
Compare
Choose a tag to compare

New

  • Broadened legal use of interfaces to allow for additional arguments on implementing fields (see graphql/graphql-spec#110)

v0.4.8

21 Oct 00:14
Compare
Choose a tag to compare

New:

  • Supports subscription in the IDL grammar and Schema representation. There is minimal support for subscriptions in the executor - at this point should still be considered experimental.

v0.4.7

02 Oct 03:17
Compare
Choose a tag to compare

Fixes:

  • Validators are aware of inline fragments without type conditions (a0bf6f9)

v0.4.6

02 Oct 03:01
Compare
Choose a tag to compare

Follows GraphQL October

New:

  • Operations without names are accepted
  • Inline fragments without type conditions are accepted

Fixes:

  • Properly export getOperationAST utility from graphql/utilities

v0.4.5

01 Oct 01:55
Compare
Choose a tag to compare

New:

  • Resolvers can now return a JavaScript Error object to indicate resolution failure. They can also return Arrays where only certain indices contain Error objects. (#178)
  • Unicode support clarified and restricted (#186)
  • getOperationAST() utility added (f66ddf5)
  • Early error if deprecation API is misused. (#185)
  • Clearer lex errors when encountering a non-printable character (#183)

Fixes:

  • Built-in Scalars and Introspection types now have descriptions
  • Input object duplicate values now parse correctly and are reported as validation errors (#184)

v0.4.4

14 Sep 19:20
Compare
Choose a tag to compare

Fixes

  • Syntax errors related to parsing of 'extend type' declaration #166

v0.4.3

02 Sep 02:34
Compare
Choose a tag to compare

New:

  • [Experimental] GraphQL parser/visitor now supports experimental type definition language.
  • [Experimental] GraphQL parser now accepts subscription as an operation kind keyword.

Fixes:

  • Type definition will no longer allow the use of invalid Name for type, field, and argument names. #145
  • Improved error messages for syntax errors relating to numbers.
  • No longer modify field definition objects provided to type definitions. #132
  • Sundry minor documentation, typo and test improvements.

v0.4.2

14 Aug 09:28
Compare
Choose a tag to compare

Fixes:

  • Improves error messaging for Syntax errors.

v0.4.1

14 Aug 08:59
Compare
Choose a tag to compare

New/Breaking:

  • Asserts that the GraphQLSchema and GraphQLType types are properly
    constructed, following the "validation" rules defined in the GraphQL Spec
    • Asserts that Objects which claim to implement an Interface actually do.
    • Schema asserts that all included types have unique names.
    • Clearer error messages when incorrect type used in GraphQLType constructors, including List and NonNull type constructors.
    • Asserts that Scalar definitions include serialization functions.
    • Removal of the graphql/type/validation submodule.
  • Asserts that the runtime Object type result of an Interface or Union typed
    field is a type is a possible type of that Interface or Union.
  • EnumType.getValues() now returns an Array.

Fixes:

  • Correctly parse Enum values from variables. #123