fix: support throwing Response.error()
#563
Merged
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.
Previously, throwing a
Response.erorr()
will fall through theinstanceof Response
check and be used as a mocked response. That would actually thrown an error.Now, we have an extra check for thrown responses, if they are a
Response.error()
, it will result in the network error (i.e. request error) just as it does if you dorequest.respondWith(Response.error())
.