-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: retry > options.maxRetries has been eliminated and only should…
…Retry is used to determine if a retry is needed.
- Loading branch information
1 parent
89cab7a
commit 0f62792
Showing
1 changed file
with
15 additions
and
8 deletions.
There are no files selected for viewing
This file contains 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
0f62792
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change looks like it stops supporting throwing the error once the max retries have been reached in the case that the error thrown is not of type
HandledError
, which kind of means pretty much every errors thrown by a back-end, or a graphql client unless we catch everything in base query and transform into HandledError. I can confirm that maxRetries have no effect whatsoever in my project, it keeps retrying indefinitely. Weird that no one has reported this however?0f62792
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@eloiqs comments on commits aren't useful and we don't keep track of those. If you have specific concerns, please file an actual issue.