packages/forms/signals/PACKAGE.md
This directory contains an experimental new Angular Forms API built on top of
signals. We're using this experimental API to explore potential
designs for such a system, to play with new ideas, identify challenges, and to demonstrate
interoperability with the existing version of @angular/forms.
We've been exploring ways that we can integrate signals into Angular's forms package. We've looked at several options, including integrating signals into template and reactive forms, and designing a new flavor of forms with signals at the core. Our hope is that we can leverage this work to close the gap between template and reactive forms, which often inspires debate in the Angular ecosystem.
Nothing is changing yet with template and reactive forms. This API is early and still highly experimental.
Even if we achieve our goals, we will roll out any changes to forms incrementally. Like with NgModules
and standalone, we don't intend to deprecate template or reactive forms without a clear sign from
our community that the ecosystem is fully on board.
No - a non-negotiable design goal of a new signal-based forms system is interoperability with existing forms code and applications. It should be possible to incrementally start using the new system in existing applications, and as always we will explore the possibility of automated migrations.