-
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
Why there are no result after CombineLatest
like this?
#3574
Comments
Shouldn't You may need to do something like
Or, with the new pipeable operators:
In order for the call to |
I think you are talking about the thing what |
The second example is different because In order for |
OK, Thank you very much! I got your point! @ibedard16 |
Actually, the problem is rather subtle and I'd say it's a bug, but perhaps not a particularly high-priority one.
With this code: const a$ = new Rx.BehaviorSubject(1);
const b$ = new Rx.Subject().combineLatest(a$);
console.log(`b$ instanceof Rx.Subject = ${b$ instanceof Rx.Subject}`);
b$.subscribe(console.log);
b$.next(1); the output will be:
So If you look at the implementation of The implementation of The problem is effected because the implementation of Not all operators are implemented this way. For example, if the const c$ = new Rx.Subject().delay(0);
c$.subscribe(console.log);
c$.next(1); |
OK, I understand. It seems that I need to learn more about the internal implementation of RxJS. Thank you very much! @cartant |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Just like demo2, I don't know what's the difference between demo1 and demo2? Why there is no result by demo2?
RxJS version:
5.3.0
Code to reproduce:
demo1:
demo2:
Expected behavior:
demo1: [1,1]
demo2: [1,1]
Actual behavior:
demo1: [1,1]
demo2: nothing
Additional information:
The text was updated successfully, but these errors were encountered: