Hi Christophe. In NG2 you have a very fine-grained control over the change detection. You can make a top-level component that decides on the fly if it's entire subtree needs to be refreshed or not. The components in this subtree can be completely unaware of this. Then there is this: The decision when something needs rendering (usually because we suspect performance issues!) is pure business logic. That is something that should NOT be in the template to begin with..
Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
