Make signal forms production ready for real world apps

[vladt22]

Which @angular/* package(s) are relevant/related to the feature request?

No response

Description

So for input type="number" model with "number | null" field is ok. But for input type="text" "string | null" is not ok? Built-in validation rules dont work with "string | null" either! Select input does not support numeric IDs for option values! But 99.9% modern apps have numbers for entity keys... We already have to review all fields and make sure undefined is not used because apparently its "bad"! But that's not enough. We now need to duplicate all our data classes just to make "signal-friendly" versions :(

I wonder what real-life enterprise-level development teams did Angular architects consulted with before declaring Signal Forms production ready?

Proposed solution

Please review signal forms and make them easier to use compared to reactive forms. Not harder!

Alternatives considered

For now we are creating custom directives with models like these:

value = model<string | null>(null);

value = model<number | null>(null);

[alxhub]

Please mind the Angular CODE_OF_CONDUCT.md.

For now we are creating custom directives with models like these:

This is the intended mechanism for implementing custom controls that interpret values differently than the native <input>, <select>, etc.

[vladt22]

For now we are creating custom directives with models like these:

This is the intended mechanism for implementing custom controls that interpret values differently than the native <input>, <select>, etc.

Could you please point me to some info where it clarifies how native with type number works with nulls?

[JeanMeche]

This just works, as of v22.

@Component({
  selector: 'app-root',
  imports: [FormField],
  template: ` <input type="number" step="0.01" [formField]="f" /> {{ f().value() }} `,
})
export class App {
  model = signal<number | null>(null);
  f = form(this.model);
}

[vladt22]

This just works, as of v22.

Right. My question was - where/how is it justified/explained that native with type="number" permits Angular to support nullable model but input with type="text" does not.