Deprecate retries
config opt in favor of retry
#422
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.
Updates the
Config
type (exposed via theUpdaterOptions
interface) to have a newfetchRetry
option which supersedes thefetchRetries
option.Whereas
fetchRetries
only accepted a numeric value (the number of times to retry the request),fetchRetry
accepts all of the options supported by the retry library which allows for more sophisticated strategies like exponential back-off.Setting
fetchRetry
is still supported, but this option may be removed in a future release.