fix(server): onError should return GraphQLFormattedError #599
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The types sent over the wire should be formatted types - specifically errors should be piped through
formatError
and the types shouldn't imply that they'reinstanceof GraphQLError
- they're just data.Warning
This is a breaking change if anyone's
onError
callback is relying oninstanceof GraphQLError
checks (seems extremely unlikely?), but otherwise it should be safe becauseGraphQLError
conforms toGraphQLFormattedError
.Tip
I don't actually care about
formatError
being called in core (feel free to revert that), I just care that the type of theonError
hook allows a formatted error be returned for consistency, and that the payload type should not imply the errors areinstanceof GraphQLError
.Note
The payloads that send
ExecutionResult
should also be sendingFormattedExecutionResult
but that seemed like a larger change so I didn't make it.