-
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
Behavior of delay
inconsistent with completions.
#4249
Comments
Core team agrees this should be fixed. |
It seems like the complete notification is always delayed right now. https://stackblitz.com/edit/rxjs-uxspew delaying complete when source is empty: delaying complete after next notifications: If I understand it correctly |
Currently,
delay
will delay the completion notification, but only if there is no nexted value (the source is "empty").This just doesn't make any sense. It should either always delay notification of complete, or it shouldn't.
Personally, I think it should not delay notification of complete, given that it's a composable behavior that way. The other way it's not, it's hard to remove the delay once it's added, because it's more obscured from downstream consumers (outside of some crazy mulitcasting scenario)
The text was updated successfully, but these errors were encountered: