Releases: enisdenjo/graphql-ws
Releases · enisdenjo/graphql-ws
v1.13.0
v1.12.0
v1.11.0
1.11.0 (2020-11-04)
Bug Fixes
- Node 10 is the min supported version (19844d7)
- Support more
graphql
versions (de69b4e) - server: Close socket if
onSubscribe
returns invalid array (#53) (0464a54) - server: Consistently set
rootValue
andcontextValue
, if not overridden (#49) (7aa3bcd) - server: Distribute server error to all clients even if one error listener throws (#56) (b96dbb9)
- server: Don't surface bad request error details in production (#55) (70317b2)
Features
Performance Improvements
v1.10.0
v1.9.3
v1.9.2
v1.9.1
v1.9.0
1.9.0 (2020-10-24)
⚠️ Deprecated
Package has been renamed from graphql-transport-ws
to graphql-ws
.
Features
BREAKING CHANGES
Should've been a major release but semantic-release
didn't detect the breaking changes of the 507a222 commit, so here we are...
This time we come with a few breaking changes that will open doors for all sorts of enhancements. Check the linked PR for more details.
Server option onSubscribe
- Now executes before any other subscribe message processing
- Now takes 2 arguments, the
Context
and theSubscribeMessage
- Now returns nothing,
ExecutionArgs
or an array ofGraphQLError
s- Returning
void
(or nothing) will leave the execution args preparation and validation to the library - Returned
ExecutionArgs
will be used directly for the GraphQL operation execution (preparations and validation should be done by you in this case) - Returned array of
GraphQLError
s will be reported to the client through theErrorMessage
- Returning
Server option validationRules
Dropped in favour of applying custom validation rules in the onSubscribe
callback. Find the recipe in the readme!
Server option formatExecutionResult
Dropped in favour of using the return value of onNext
callback.
v1.8.2
1.8.2 (2020-10-22)
⚠️ Deprecated
Package has been renamed from graphql-transport-ws
to graphql-ws
.
Bug Fixes
- server: No need to bind
this
scope (f76ac73)