fix(interceptor): handle the error in the same interceptor #6269
+79
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes: #4537
When handling error in asynchronous request interceptors,
onRejected
always handle the error in the next interceptors. So I make a fix about this case. Detail context is in the issue.During the fix, I found that it will cause a TypeError when an error occurred in the request interceptors, because the config is lost during the promise chain.
So we can define a new
onRejected
handler behavior. If users want to continue the request, they should return a default config in theonRejected
function.