change incorrect subscribe return type to a GraphQLError#3621
change incorrect subscribe return type to a GraphQLError#3621yaacovCR merged 1 commit intographql:mainfrom
Conversation
✅ Deploy Preview for compassionate-pike-271cb3 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
30f6596 to
e8fcbcc
Compare
IvanGoncharov
left a comment
There was a problem hiding this comment.
I'm for it 👍
Currently, the subscription algorithm doesn't mention this check at all:
https://spec.graphql.org/draft/#sec-Source-Stream
I don't see how this change is contradict spec, so I'm for merging it.
But if you think previous behavior was contradicting the spec it's valuable to document please update the description with links to the spec and more details on what contradiction is.
@yaacovCR Otherwise feel free to merge.
|
I think fixing the entire spec in terms of how it clarifies errors is beyond the scope of this PR. See also graphql/graphql-spec#894 And the entire Fundamentally, however, I imagine that the spec purports there to be unified behavior as much as possible between all operations, as within the spec they are all considered different forms of execution, with subscriptions simply a different operation type. That is why this PR, which is one of several on the road toward integrating subscriptions into More specifically, there is a rough equivalence given between In my opinion. :) |
…a systems error to match spec (in parallel to field-level resolver errors in execute) note the addition of the path, as execution has begun
e8fcbcc to
277b5fa
Compare
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (graphql#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…a systems error (#3621) ...in parallel to field-level resolver errors within the non-subscription execution algorithm. Note the addition of the path, an at-least rough correspondence to field execution initiation.
…rather than a systems error
to match spec (in parallel to field-level resolver errors in execute)
note the addition of the path, as execution has begun