Skip to content

Commit 4beaddc

Browse files
agale123josephperrott
authored andcommitted
docs(upgrade): expand upon change detection implications for downgraded components (angular#39100)
PR Close angular#39100
1 parent 89c5255 commit 4beaddc

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

aio/content/guide/upgrade.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -479,6 +479,15 @@ using the `downgradeComponent()` method. The result is an AngularJS
479479
<code-example path="upgrade-module/src/app/downgrade-static/app.module.ts" region="downgradecomponent" header="app.module.ts">
480480
</code-example>
481481

482+
<div class="alert is-helpful">
483+
484+
By default, Angular change detection will also run on the component for every
485+
AngularJS `$digest` cycle. If you wish to only have change detection run when
486+
the inputs change, you can set `propagateDigest` to `false` when calling
487+
`downgradeComponent()`.
488+
489+
</div>
490+
482491
Because `HeroDetailComponent` is an Angular component, you must also add it to the
483492
`declarations` in the `AppModule`.
484493

0 commit comments

Comments
 (0)