-
Notifications
You must be signed in to change notification settings - Fork 524
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
Ignoring events in subscription resolver #1181
Comments
Hi @benwilson512, I'm writing here because of your comment on my PR #1309. I must have missed the error in the playground because I didn't have it in the graphql document, so it looked like it was only sending the null without information about the error. You also wrote that you had a plan for this in mind using a special return value, I would be happy to take a stab at implementing that if you could give me a couple pointers on what your where thinking. |
Hello there!
Currently when a subscription is resolved, we have no way of ignoring events for individual subscriptions.
This would be useful to avoid notifying clients when:
For example, consider this subscription:
Related request: #365 (comment)
The text was updated successfully, but these errors were encountered: