-
Notifications
You must be signed in to change notification settings - Fork 3k
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(repeat): now has configurable delay #6640
Conversation
Adds a feature to `repeat` to match the configurable API of `retry`. `repeat` can now be used in a similar manner to `repeatWhen`, only perhaps in a more developer-friendly way. - Also updates `repeat` tests to use run mode.
related #6367 |
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.
Maybe we should add a test that shows that empty notifiers are not treated as signals?
Doesn't this create unnecessary verbosity?
Let's better update the timer(2000)
.pipe(
tap({
subscribe: () => console.log('subscribe'),
complete: () => console.log('complete'),
}),
repeatWhen(pipe(delay(1000)))
)
.subscribe(() => console.log('next')); |
spec/operators/repeat-spec.ts
Outdated
const expected = '|'; | ||
rxTest.run(({ cold, expectObservable, expectSubscriptions }) => { | ||
const e1 = cold('--a--b--| '); | ||
const unsub = ' !'; |
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 is not properly converted - though, unsub
is not really needed.
Adds a feature to
repeat
to match the configurable API ofretry
.repeat
can now be used in a similar manner torepeatWhen
, onlyperhaps in a more developer-friendly way.
repeat
tests to use run mode.