Releases: graphql/graphql-js
Releases · graphql/graphql-js
v0.10.4
New:
- Inline invariant transform for faster loading of schemas (#935)
- Support for directives applied on IDL & Schema (#746)
- Account for query's offset in file for errors (#949)
v0.10.3
New:
- Additional detection in
findBreakingChanges()
(#874)
- Experimental Schema Language now allows a leading pipe in union definitions (#907, #911)
- A
printIntrospectionSchema()
utility is now exported (#905)
- A
getDirectiveValues()
utility is now exported (a1f6308)
Fixed:
- Improvements to error messages
- Removes trailing commas from source so it can experimentally be used directly (86009a6)
v0.10.1
New:
- Spec compliance: Continued progress towards Subscription support, adding Validation rules (#882)
Fixed:
- Better handling of Errors from
execute()
function, returning resolved GraphQL responses instead of rejected promises for spec-described errors. (#883)
- Fixed flow issues when using GraphQL.js with some optional configuration with Flow v47 (#885)
v0.10.0
New
isValidValue()
and isValidLiteral()
added to Scalar and enum types (#861).
- You can now set a custom default field resolver (#865).
graphql()
may now take a Source
object, in addition to the existing support for string
(#866).
graphql()
may now take an object with named parameters (#867).
- Partial support for GraphQL subscriptions (#846, #868) (Not yet ready for production use).
Breaking
- Spec compliance: forbid duplicate type definitions (#744).
- Spec compliance: disallow inappropriate coercion of non-
Int
values to Int
(#837).
Fixes
- Ensure
GraphQLError
stack trace includes error message (#718).
- Fix input coercion to allow null-valued Enums as arguments (#848).
- Fix for fields that are JavaScript keywords (#864).
- Compatibility with Flow v0.47.0 (#878).
v0.9.6
New
- It is now possible to suppress warnings about non-spec compliant names by setting the
GRAPHQL_NO_NAME_WARNING
environment variable. This may be useful when working with legacy schemas.
v0.9.5
New:
- Much improved Flow types from the experimental
%checks
type (#695)
- Allow passing a custom
TypeInfo
instance to validate()
(#834)
- Exported
getVisitFn
for building custom composite visitors. (#807)
Fixes:
- Allow Enum internal values to be
false
, null
, and undefined
(#836)
v0.9.4
New:
- All validation rules are now exported directly (#808)
Fixes:
- Fix flow issue with constructing
new GraphQLError()
(#829)
Spec Compliance:
- Now throws error when building Enum with reserved words (#812)
- Now throws error when building Union with multiple of the same type (#813)
- Now throws error when building Object type implementing the same Interface more than once (#728)
v0.9.3
Fixes
- Eliminate false positives reported by
findArgChanges
(#783).
v0.9.2
Breaking
- Remove ambiguity in
isLeafType
check: it no longer performs named type unwrapping and is consistent with the other isCompositeType
/isAbstractType
checks (#697).
New
- Make wording in error messages more consistent (#767).
- Allow deprecated fields/values to be extended (#755).
- Validation messages about names starting with double underscores are now use
console.warn
rather than console.error
(#717).
- Improved the error message for undefined field config (#702).
- The
findBreakingChanges
validation now reports breaking changes made to arguments (#701).
Internal
- Performance improvements to the
separateOperations
module (#710).
- Improvements to Flow checking (#699) and type safety (#698).
v0.9.1
Fixes
- Downgrade error to warning for non-spec-compliant use of non-meta fields starting with
__
(#692).
- Workaround for problem in some environments with reserved literals (such as
default
) being used as properties (#693).