Add an 'onError' handler - #51
Merged
Merged
Conversation
… to a server error
Collaborator
|
Thanks @pgengler! |
Collaborator
|
Published as v1.4.0 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This add an
onErrorhook that can be used to do something if the request fails (it's optional, and by default just contains the existing "on error" logic of logging the error in non-test environments).(The real-world use case for this is to be able to tell when the endpoint response is a 403, usually meaning the user's session has expired, so we can redirect them back to the login page without the user having to try to perform some action first.)