Releases: graphql/graphql-js
Releases · graphql/graphql-js
v0.11.2
v0.11.1
v0.11.0
Breaking
- The
subscribe()
function now returns aPromise
of either anAsyncIterator
orExecutionResult
to better distinguish between initialization errors and publish errors; previously it just returned anAsyncIterator
(#918).
Spec compliance
- Passing an array in place of a
String
input throws an error instead of silently coercing (#925).
Fixes
- Directive descriptions are preserved through calls to
extendSchema()
(#961).
Changes
v0.10.5
v0.10.4
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:
v0.10.0
New
isValidValue()
andisValidLiteral()
added to Scalar and enum types (#861).- You can now set a custom default field resolver (#865).
graphql()
may now take aSource
object, in addition to the existing support forstring
(#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 toInt
(#837).