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.

v0.2.1

Fixes:

• Removes flow comments from npm published JS. Unfortunately the flow-comment transpiler is too buggy at this point in time.

v0.2.0

New:

• Flow types are included in the npm release in the form of flow-comments. Flow will find and utilize these when you install graphql-js via npm, and if you don't use flow then it's business as usual.
• GraphQL Type predicates for common groupings are now exported from graphql/type.
• A new submodule graphql/language/schema for parsing and working with the GraphQL schema language.
• The submodule graphql/utilities was included which adds a lot of useful functions for building client tools.
  • A definitive full introspection query.
  • Build a client-side GraphQLSchema instance from an introspection result.
  • Build a client-side GraphQLSchema from GraphQL Schema language.
  • Print a GraphQLSchema to GraphQL Schema language.
  • Create a GraphQLType instance from GraphQL Schema language.
  • Create a JavaScript value from a GraphQL language value.
  • Create a GraphQL language value from a JavaScript value.
  • A smart visitor which maintains type information as it visits the GraphQL document AST.
  • Utilities to determine if a JavaScript value or GraphQL language value adhere to a GraphQL type.
• Minor re-organization of submodules.

v0.1.12

No changes