You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/docs/cdk/render-strategies/strategies/basic-strategies.md
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -97,8 +97,8 @@ This means for every emitted value [`ChangeDetectorRef#markForCheck`](https://gi
97
97
Angular still needs zone.js to trigger the [`ApplicationRef#tick`](https://github.com/angular/angular/blob/7d8dce11c0726cdba999fc59a83295d19e5e92e6/packages/core/src/application_ref.ts#L719) to re-render,
98
98
as the internally called function [`markViewDirty`](https://github.com/angular/angular/blob/930eeaf177a4c277f437f42314605ff8dc56fc82/packages/core/src/render3/instructions/shared.ts#L1837) is only responsible for dirty marking and not rendering.
99
99
100
-
| Name | Zone Agnostic | Render Method | Coalescing | Scheduling |
@@ -112,17 +112,17 @@ As detectChanges has no coalescing of render calls
112
112
like [`ChangeDetectorRef#markForCheck`](https://github.com/angular/angular/blob/930eeaf177a4c277f437f42314605ff8dc56fc82/packages/core/src/render3/view_ref.ts#L128) or [`ɵmarkDirty`](https://github.com/angular/angular/blob/930eeaf177a4c277f437f42314605ff8dc56fc82/packages/core/src/render3/instructions/change_detection.ts#L36) have, we apply our own coalescing, 'scoped' on component level.
113
113
114
114
Coalescing, in this very manner, means _collecting all events_ in the same
115
-
[EventLoop](https://developer.mozilla.org/de/docs/Web/JavaScript/EventLoop) tick, that would cause a re-render. Then execute re-rendering only _once_.
115
+
[EventLoop](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Event_loop) tick, that would cause a re-render. Then execute re-rendering only _once_.
116
116
117
117
'Scoped' coalescing, in addition, means _grouping the collected events_ by a specific context.
118
118
E. g. the _component_ from which the re-rendering was initiated.
119
119
120
120
This context could be the Component instance or a `ViewContextRef`,
121
121
both accessed over the context over `ChangeDetectorRef#context`.
122
122
123
-
| Name | Zone Agnostic | Render Method | Coalescing | Scheduling |
The best place to use the local strategy is a structural directive like `*rxLet`. Those will have a independent template from the component and perform changes only there.
128
128
@@ -138,7 +138,7 @@ The no-operation strategy does nothing. It can be a valuable tool for performanc
138
138
139
139
| Name | Zone Agnostic | Render Method | Coalescing | Scheduling |
0 commit comments