Angular Recasts Signals as State Primitive, Debuts Signal Forms API With 1 Model Source
Updated
Updated · InfoWorld · Jun 4
Angular Recasts Signals as State Primitive, Debuts Signal Forms API With 1 Model Source
2 articles · Updated · InfoWorld · Jun 4
Summary
Angular’s latest guidance says Signals should model current state and explicit dependencies, not act as a lighter RxJS-style event stream.
In the pull-based model, a signal change marks dependent computations stale and recomputes them on next read, avoiding subscription order, missed emissions and listener management.
The new Signal Forms API applies that approach by treating a writable model signal as the single source of truth, then layering validation, interaction state and submission semantics through form().
Field status such as invalid(), errors() and pending() is exposed as derived signals, while built-in rules like required() and email() reevaluate automatically as underlying values change.
Angular positions Signals and RxJS as complementary tools—Signals for deterministic state derivation, RxJS for async streams, external events and side effects—with a follow-up article set to show component integration.