graphql 0.3.0
Breaking/New:
isTypeOfis now called (if defined) to assert that GraphQL object types are executing against the correct values #38- Field
resolvefunctions now have a new API:resolve(value, args, info), whereinfois 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.errorsis now a list ofGraphQLErrorinstances, 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
nullfor these arguments and fields. - Scalar definition
coerceandcoerceLiteralhave been renamed toserializeandparseLiteralrespectively. - Scalar definitions may now define
parseValuewhich is used when interpreting variable values of that type. Previouslycoercewas 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.