-
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
skipUntil(s$) doesn't complete when s$ completes #5379
Comments
If the notifying observable completes before emitting a notification, it should not complete the observable to which the operator has been applied, so this looks to be the correct behaviour, to me. There are other issues related to this, as the behaviour of some other operators differs and is incorrect. Changes to make operators that use notifier behave in a consistent manner are going to be made in the next major version and I've listed some in this issue: #5372 |
Fyi it's documented behavior: https://github.com/ReactiveX/rxjs/blob/master/src/internal/operators/skipUntil.ts#L13 |
this is expected behavior. The notifier must notify. An observable that completes without emitting a value is "empty" and will never notify. In fact, it's an |
Bug Report
Current Behavior
The
skipUntil(x$)
operator does not cause the resulting observable to complete whenx$
completes before it emits a value.Reproduction
Expected behavior
I would expect
s$
to complete as soon as stopper$ completes, and displays$ complete
on the browser window immediately afterstopper$ complete
shows.s$
could have many subscribers, and a heavy source observable, and I think that it not competing causes a completely useless waste of resources.Environment
Additional context/Screenshots
Output of the above script:
The text was updated successfully, but these errors were encountered: