feat: treat unhandled interceptor exceptions as 500 responses #532
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.
Much like request handlers in MSW, everything you write in your interceptors is from the server's perspective. If an exception happens on the server, it's usually handled gracefully as the 500 error response to the client. This consistency is nice for predictability but also aligned behavior across the low-level Interceptors and high-level MSW.
Changes
request
listeners are now coerced to500 Unhandled Exception
mocked error response to emulate server suffering an exception.request.respondWith(Response.error())
.