Detaching the change detector from components

In the previous recipe, we learned how to use the OnPush strategy in our components to avoid Angular change detection running unless one of the @Input() bindings has changed. There is, however, another way to tell Angular to not run change detection at all for a particular component and its subtree. This cuts the component and its subtree from the change detection cycle completely, as shown in Figure 12.5, which can result in an increase in the overall performance. This is also handy when you want full control of when to run change detection. In this recipe, you’ll learn how to completely detach the change detector from an Angular component to gain performance improvements.

Figure 12.5: Change detector detached from component tree

Getting ready

The app that we are going to work with resides in start/apps/chapter12/ng-cd-ref inside the cloned repository:

1. Open the code repository in your code editor.
...