Signal Forms Support

[AhmedAl-Majidi]

Are there any plans or an active roadmap to introduce Signal Forms support across Optimus UI form components?

[geromegrignon]

Hi @AhmedAl-Majidi,

We aim to start modernizing the codebase this week to Signals as a prerequisite for Signal Forms support.
We might land Signal Forms support this week too as a next prerelease version.

It'll will be more likely authored as 3.0.0 version as it could introudce breaking changes, even if the new FormValueControl API is backwards compatible with Reactive Forms and ngModel.

[raven-dever]

Signal Forms Proposal:
I propose to repurpose the existing Classes that currently implement FormValueAccessor interface for the Form Components:
BaseModelHolder / BaseEditableHolder / BaseInput as abstract classes to adhere to Angular's FormValueControl interface. BaseModelHolder ultimately defines the type for the value model as an abstract class member and the Component or Directive that extends these classes should implement the value model itself. The type_for the value model input can be constraint (or derived from Generics) via the Generic ModelValue. The FormValueControl fields touch (important for blur-options for both Signal or Reactive Forms) , focus, reset have to be implemented individually.

Diff compare of my current prototype branch for the currently relevant classes: main...raven-dever:signal-forms-optimus-ui-proposal

In my proposal BaseEditableHolder would also be able to be configured nullable or nonnullable via class Generic isNullable and its input nullable(could maybe defined as a optional class member of BaseEditableHolder, to be individually implemented on Components/Directives). Because multiple components currently set the form value to null (MultiSelect, Autocomplete, ...) when clearing or resetting. With a Generic input, it can be decided individually if Components and Directive would reset to null or an initial "empty value" (ie empty String, Array or Record).

If FormValueControl interface is properly implemented, be either through this or another proposal, I'd suggest to remove any code reliant injecting NgControl. For instance the Textarea component has a direct incompatibilty to Signal Forms because it relies on NgControl to retrieve the Control value: #203
Value, validation, touch or other states will be directly available via the FormValueControl interface