-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove defer/stream support from subscriptions #3742
Remove defer/stream support from subscriptions #3742
Conversation
✅ Deploy Preview for compassionate-pike-271cb3 ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Hi @robrichard, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
e528a7e
to
5a674d0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than possibly tweaking a comment, these changes look good to me.
More generally, I am also fine with leaving incremental delivery support with subscriptions for a potential later stage to help advance the initial release.
5a674d0
to
7fc599f
Compare
7fc599f
to
081f177
Compare
@IvanGoncharov this is ready for review, now implementing what was discussed at the November 2022 (Secondary, EU) WG. The spec PR has also been updated to reflect this. |
081f177
to
ebb5efb
Compare
Discussion topic: graphql/defer-stream-wg#55
This implements what was agreed on in the November 2022 (Secondary, EU) WG. There was consensus to move forward with disabling defer/stream on subscriptions via a field error. This also adds a new validation rule that prevents @defer or @stream from being used inside a subscription operation without an if argument that can be used to disable defer/stream.