mirror of
https://github.com/angular/angular
synced 2026-05-24 09:28:37 +00:00
bf1c12cd93
Previously, navigating a `FieldTree` in signal forms involved reactive reads
of the value of the parent field(s), both directly and via `.childrenMap()`.
This meant that on _any_ change to the value of a field, reactive
notifications would trigger updates of computeds, reruns of effects, etc.
So for example, this effect would run on every change to the form:
```ts
const f = form(signal({data: 'abc', unrelated: 0}));
effect(() => {
// accessing f.data incurs a dependency on f().value() which changes
// on every change in the whole form
console.log(f.data().value());
});
```
This is deeply counterintuitive and troublesome when attempting to write
effect logic, and also results in `computed`s unnecessarily updating.
This change introduces the concept of a "reader" computed, which memoizes
the access of a field at a given key via the reactive graph. With this, the
same `f.data` access above now depends on the `data` reader in `f` only,
which is effectively a constant computed. As a result, the effect only
reruns on changes to `data`'s value, as intended.
PR Close #65802
|
||
|---|---|---|
| .. | ||
| api | ||
| compat | ||
| BUILD.bazel | ||
| dynamic.spec.ts | ||
| field_context.spec.ts | ||
| field_node.spec.ts | ||
| field_proxy.spec.ts | ||
| form.spec.ts | ||
| logic_node.spec.ts | ||
| path.spec.ts | ||
| recursive_logic.spec.ts | ||
| resource.spec.ts | ||
| submit.spec.ts | ||
| types.spec.ts | ||
| validation_status.spec.ts | ||