mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
ffad7b8ea9
One downside of implicit dependency tracking in `effect()`s is that it's easy to for downstream code to end up running inside the effect context by accident. For example, if an effect raises an event (e.g. by `next()`ing a `Subject`), the subscribers to that `Observable` will run inside the effect's reactive context, and any signals read within the subscriber will end up as dependencies of the effect. This is why the `untracked` function is useful, to run certain operations without incidental signal reads ending up tracked. However, knowing when this is necessary is non-trivial. For example, injecting a dependency might cause it to be instantiated, which would run the constructor in the effect context unless the injection operation is untracked. Therefore, Angular will automatically drop the reactive context within a number of framework APIs. This commit addresses these use cases: * creating and destroying views * creating and destroying DI injectors * injecting dependencies * emitting outputs Fixes #54548 There are likely other APIs which would benefit from this approach, but this is a start. PR Close #54614 |
||
|---|---|---|
| .. | ||
| security | ||
| array_utils.ts | ||
| assert.ts | ||
| BUILD.bazel | ||
| char_code.ts | ||
| closure.ts | ||
| coercion.ts | ||
| comparison.ts | ||
| decorators.ts | ||
| dom.ts | ||
| empty.ts | ||
| errors.ts | ||
| global.ts | ||
| is_dev_mode.ts | ||
| iterable.ts | ||
| lang.ts | ||
| ng_dev_mode.ts | ||
| ng_i18n_closure_mode.ts | ||
| ng_jit_mode.ts | ||
| ng_reflect.ts | ||
| noop.ts | ||
| performance.ts | ||
| property.ts | ||
| raf.ts | ||
| stringify.ts | ||