Formcontrol essential features about angular HOT 3 OPEN

Hi @Dejavu333 ,

I don't understand the motivations of the following points, maybe could explain it a little more :

1.Formcontrol should know whether it is focused, submitted.

The focused property can easily find a utility, but for the submit, what use cases have you in mind (for the FormControl particulary, as for the FormGroup it can find a useful usage) ?
Anyway the [formGroup] directive has an property that track the submit status :

<form [formGroup]="form" (ngSubmit)="submit()" #formDir=ngForm>
    <input type="text" formControlName="test" />
    <button type="submit">submit</button>
  </form>
  <span>{{formDir.submitted}}</span>

What have you in mind for the focus event ?

2.We should be able to add multiple updateOn values not just one.

Does it make any sense to have a stream for the focus event anymore ? What are you planning to listen for the focus event ? I think that the events streamed for the update should be bounded to avoid any overload during the listening of events.

The third point makes sense.

from angular.

1 and 2 kinda goes hand in hand.
Currently, FormControl validations are tightly coupled and can only be triggered by a single event, which limits flexibility. For instance, you might want to trigger different validators for FormGroup and FormControl, but the current setup doesn’t allow for this differentiation, since the updateValueAndValidity function triggers valueChanges in the parent FormGroup, which in turn activates its validators. This becomes an issue when you want your controls' validators to be triggered by different events - for example, one on ‘blur’ and ‘hover’ (this is where multiple values would come into play), another on ‘change’, and the FormGroup validators on ‘submit’ and ‘submit’ only.

It would be beneficial to decouple these elements to allow for more granular control over when and how validations are triggered.

from angular.

I've started to implement a new approach, where you can instantiate a formControl like this:

Cleaner and can achieve the desired behaviour I stated above.

from angular.