-
Notifications
You must be signed in to change notification settings - Fork 6
integrate well with Angular2 #11
Comments
btw, I'm happy with moving/integrating code from/to/with angular change detector code. At the very least, testing that the integration works well. Fun history: a very old version of this library was called "watcher" and was ported by @sigmundch from Angular1 :). For better or worse we got pulled in the ES7 O.o direction, but this library was inspired by Angular. There's something poetic about it returning to its roots with Angular2 integration. |
Even funnier: Angular 1's watchers are considered broken and being removed from Angular 2. Angular 2's tree pruning works by marking branches of the component tree as dirty whenever a node notifies the change detection system that it is dirty. |
@yjbanov, is it possible we could get Victor from Angular to work with John in the near future? I'd be happy to help, of course, but it might be more effective for the change detector guy to work on the change detector :) |
@vsavkin please prepare to answer John's questions :) @matanlurey I'm assuming this issue is about performance. Could you summarize your findings and point out issues? |
from @matanlurey at #9 (comment)
it sounds like #10 is the first step, and favoring a simple ChangeNotifier over Observable. What else can we do?
The text was updated successfully, but these errors were encountered: