Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(retry): add config to reset error count on successful emission #5280

Merged
merged 5 commits into from
Feb 3, 2020

Conversation

cartant
Copy link
Collaborator

@cartant cartant commented Jan 30, 2020

Description:

This PR cherry picks commits from #4683 but removes/reverts the unnecessary changes made to the package.json and the testing infrastructure. And removes the merge commit.

Related PR: #4683

ommizrah and others added 4 commits January 30, 2020 19:34
This PR adds the ability to reset the error counter on successful emissions using the `retry`
operator. The current behavior for `retry(n)` is to call error if n errors occurred, regardless of
whether or not they were consecutive. Now one would be able to use `retry(n, true)` to have the
count reset so that only n consecutive errors will cause the observable to fail.
added overloaded signature to the `retry` operator that accepts a config object
@cartant cartant changed the title [WIP] feat(retry): add config to reset error count on successful emission feat(retry): add config to reset error count on successful emission Jan 30, 2020
@cartant cartant marked this pull request as ready for review January 30, 2020 09:55
@cartant cartant requested a review from benlesh January 30, 2020 09:55
@benlesh benlesh merged commit ab6e9fc into ReactiveX:master Feb 3, 2020
kwonoj pushed a commit to kwonoj/rxjs that referenced this pull request Feb 5, 2020
…eactiveX#5280)

* feat(retry): add config to reset error count on successful emission

This PR adds the ability to reset the error counter on successful emissions using the `retry`
operator. The current behavior for `retry(n)` is to call error if n errors occurred, regardless of
whether or not they were consecutive. Now one would be able to use `retry(n, true)` to have the
count reset so that only n consecutive errors will cause the observable to fail.

* feat(retry): add config parameter

added overloaded signature to the `retry` operator that accepts a config object

* chore: restore package-lock.json

* chore: appease TypeScript

* chore: revert change to Observable spec
martinsik pushed a commit to martinsik/rxjs that referenced this pull request Feb 15, 2020
…eactiveX#5280)

* feat(retry): add config to reset error count on successful emission

This PR adds the ability to reset the error counter on successful emissions using the `retry`
operator. The current behavior for `retry(n)` is to call error if n errors occurred, regardless of
whether or not they were consecutive. Now one would be able to use `retry(n, true)` to have the
count reset so that only n consecutive errors will cause the observable to fail.

* feat(retry): add config parameter

added overloaded signature to the `retry` operator that accepts a config object

* chore: restore package-lock.json

* chore: appease TypeScript

* chore: revert change to Observable spec
@lock lock bot locked as resolved and limited conversation to collaborators Mar 10, 2020
@cartant cartant deleted the retry branch September 24, 2020 07:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants