Skip to main content

GraphQL Subscriptions should handle errors in the source stream

At a glance​

Timeline​


Currently if sourceStream generates an error, then responseStream repeats the error. This is the behavior implemented in graphql-js and is problematic.

GraphQL captures execution errors and wraps them in an { errors: [...] } payload for query and mutation operations; it should do the same for stream errors in a subscription operation.

This PR makes this behavior explicit.