Open
Conversation
|
proposal: rename it to |
Author
|
Agreed, renamed to |
Author
|
@pi0 this is ready for review when you get a moment! |
ad22b48 to
5993edb
Compare
cbba814 to
a8d70ab
Compare
|
This would be helpful because sometimes we can't know just from the HTTP status if it's safe to retry. I hope this PR or #359 can be merged soon. |
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
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.
Resolves #503
Summary
This PR adds support for
retryConditionoption for$fetch.What’s new
retryCondition(context)callback for custom retry logic.retryStatusCodesandretryConditionindependent — retries if either is satisfied.retryConditionthrows, the error is propagated to the consumer.Example