angular/packages/forms/signals
Miles Malerba 60c8e2779c refactor(forms): preserve logic order when apply is used on root path
In some cases the logic order was not preserved properly when using `apply`. In particular this occurs when some logic is registered on a child of the root, followed by an apply to the root, followed by further logic registered on a child. In this case the final registered logic wound up running before the applied logic.

This happened because `FieldPathNode` for a child path was caching its `LogicNodeBuilder` at creation time. This meant that if the parent's `LogicNodeBuilder` changed (e.g., due to an `apply` call), the child would still be using the old one.

This commit fixes the issue by dynamically resolving the `LogicNodeBuilder` for a child path whenever it is accessed.

(cherry picked from commit fa13a167f1)
2025-10-29 10:40:09 +01:00
..
src refactor(forms): preserve logic order when apply is used on root path 2025-10-29 10:40:09 +01:00
test refactor(forms): preserve logic order when apply is used on root path 2025-10-29 10:40:09 +01:00
BUILD.bazel build: configure signal forms for release (#63458) 2025-08-29 14:31:35 -07:00
index.ts feat(forms): add experimental signal-based forms (#63408) 2025-08-28 09:02:43 -07:00
PACKAGE.md build: configure signal forms for release (#63458) 2025-08-29 14:31:35 -07:00
public_api.ts refactor(forms): rename files related to metadata (#64603) 2025-10-23 18:13:16 +02:00