mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
38c9f08c8d
Previously effects were queued as they became dirty, and this queue was flushed at various checkpoints during the change detection cycle. The result was that change detection _was_ the effect runner, and without executing CD, effects would not execute. This leads a particular tradeoff: * effects are subject to unidirectional data flow (bad for dx) * effects don't cause a new round of CD (good/bad depending on use case) * effects can be used to implement control flow efficiently (desirable) This commit changes the scheduling mechanism. Effects are now scheduled via the microtask queue. This changes the tradeoffs: * effects are no longer limited by unidirectional data flow (easy dx) * effects registered in the Angular zone will trigger CD after they run (same as `Promise.resolve` really) * the public `effect()` type of effect probably isn't a good building block for our built-in control flow, and we'll need a new internal abstraction. As `effect()` is in developer preview, changing the execution timing is not considered breaking even though it may impact current users. PR Close #51049 |
||
|---|---|---|
| .. | ||
| container.ts | ||
| context.ts | ||
| defer.ts | ||
| definition.ts | ||
| document.ts | ||
| i18n.ts | ||
| injector.ts | ||
| lview_tracking.ts | ||
| node.ts | ||
| projection.ts | ||
| public_definitions.ts | ||
| query.ts | ||
| renderer.ts | ||
| renderer_dom.ts | ||
| sanitization.ts | ||
| styling.ts | ||
| type_checks.ts | ||
| view.ts | ||