-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Ensure subscriptions adhere to the errorPolicy
#11162
Conversation
🦋 Changeset detectedLatest commit: 6110dc3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
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.
@jerelmiller and I synced offline on this - LGTM 👍
Fixes #10559
Errors returned in subscriptions payloads are always thrown, regardless of the error policy. With this change, the
next
function is now called if theerrorPolicy
is set toall
orignore
. In the case ofignore
, theerrors
property is stripped off the result.NOTE: Protocol errors are still thrown regardless of the error policy. According to our docs,
errorPolicy
only changes how GraphQL errors are handled.NOTE:
useSubscription
andsubscribeToMore
do not currently allowerrorPolicy
as a valid option, so these are not tested with this change. Since that is technically a new "feature", I've opted to wait to add this functionality in a patch release and instead will consider this as part of the next minor release. See #11165 to track the progress on this missing functionality.Checklist: