Differences between value and ngValue in Angular 5
Today I realized about an unexpected (for me) behaviour of the reactive forms in Angular 5. The server was receiving from the app an string with the value "null" instead of the null value, whichh is what I wanted.
I did the following test:
https://stackblitz.com/edit/angular-rjrspr?file=app%2Fapp.component.html
As you can see in the picture below, if I use [value]="null" in the select, the field is getting "null" (string literal) as value. However, if I use [ngValue]="null" it gets the expected null value.
I thought that using value was intended for reactive forms, while ngValue was for template driven forms. I'd like to know if it's safe to use both in my forms (I always use reactive forms) and if there's any explanation for the different behaviour.
Thanks!
Answer
Its ok to use valueor ngValue.
The only difference between two is that value is always string, where in ngValue you can pass object