ObservableCursor won't work with AsyncPipe about meteor-rxjs HOT 7 CLOSED

It actually not needed to be bind to a zone, because that's what AsyncPipe should do... weird...
I will debug it soon.
@kamilkisiela

from meteor-rxjs.

@kamilkisiela I added a new examples directory with angular2 example - it works there great. Also tested with ChangeDetectionStrategy.OnPush and it works.

from meteor-rxjs.

@dotansimha how does ChangeDetectionStrategy.OnPush relate to this? AsyncPipe doesn't run zone it only marks itself for check (https://github.com/angular/angular/blob/14ee75924b6ae770115f7f260d720efa8bfb576a/modules/%40angular/common/src/pipes/async_pipe.ts#L146).
Vile thing here is that it might seem working for simple examples (when everything happens synchronously), but will fail eventually for more complex once.
There was also an idea to implement own version of AsyncPipe that runs zone.

from meteor-rxjs.

Yeah you are right about OnPush. Do you have an example for a complex scenario? I tried some and it looks like it worked in all of them.

from meteor-rxjs.

@dotansimha I checked and turned out that Meteor.subscribe's callback runs now always in the zone (didn't before). I think the issue can be in the promises. Before Meteor promise could be initialized before zone-aware promise, so it was not patched. Zone.js actually patches everything including websockets. But that peace with promises was lost from patching.

from meteor-rxjs.

@barbatus thanks, I see.
Do you have any way to reproduce? I wan't to have a look on it

from meteor-rxjs.

@dotansimha I am saying I missed this point before. Now .zone probably not needed at all, except if observables are used out of Angular 2 zone. I'll check it out one more time and probably cleanup some stuff that not needed.

from meteor-rxjs.