-
Notifications
You must be signed in to change notification settings - Fork 564
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
fix: response error interceptor broken #3805
Conversation
return (dispatch) => { | ||
return function Intercept (opts, handler) { | ||
return dispatch(opts, new ResponseErrorHandler(opts, { handler })) | ||
} | ||
} |
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.
Hmm, this makes me having stomach ache
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.
Care to elaborate or give a suggestion?
When we are already touching this file massively, should we extract the handler into a new file and put it into the handler folder? |
It depends on what we do with that handler. |
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.
lgtm
This relates to...
The response-error interceptor
Rationale
The interceptor is currently broken since Request no longer accepts
throwOnError
as an option.Changes
throwOnError
as it is considered an invalid argument.Features
Bug Fixes
Breaking Changes and Deprecations
Status