v0.4.3

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

Fixes:

• Improves error messaging for Syntax errors.

v0.4.1

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

v0.3.0

Breaking/New:

• isTypeOf is now called (if defined) to assert that GraphQL object types are executing against the correct values #38
• Field resolve functions now have a new API: resolve(value, args, info), where info is an object which contains the same information which used to be separate arguments, and includes more useful stuff! https://github.com/graphql/graphql-js/blob/master/src/type/definition.js#L359
• graphql() no longer formats its errors. result.errors is now a list of GraphQLError instances, which provides useful information including stack traces.
• Arguments and Input Object Fields not provided are not set on the internal JS objects. The previous behavior was to set null for these arguments and fields.
• Scalar definition coerce and coerceLiteral have been renamed to serialize and parseLiteral respectively.
• Scalar definitions may now define parseValue which is used when interpreting variable values of that type. Previously coerce was being reused for this purpose.

Fixed:

• Nested input objects are no longer excluded by introspection.
• Fix issue where a fragment spread with missing definition breaks the validator.

v0.2.6

New:

• Adds all validation rules for uniqueness recently added to the GraphQL spec.

Fixed:

• formatError is exported directly from graphql.
• One validation error no longer causes spurious failures of other validations.
• Directive arguments no longer incorrectly invalidate.
• Validation errors have slightly improved messages.

v0.2.5

Fixes:

• Fix issue with buildASTSchema when floats are used. (#104)
• Fix issue with buildASTSchema when invalid mutation is passed.
• Fix issue with buildASTSchema when type is only referenced via interface.

v0.2.4

Fixes:

• Update print-schema script to work with refactored schema module.
• Fix issue with buildASTSchema when both query and mutation are passed. (#100)

0.2.3

Temporary push to fix mismatch between package.json and tags.

v0.2.3

Fixes:

• Ensure graphql-js doesn't rely on ES6 prototype methods (#99)

v0.2.2

Fixes:

• Fix case reported by @steveluscher where overlapping fragments could incorrectly invalidate.