Options for the NgForm instance. Accepts the following properties:
updateOn: Serves as the default updateOn value for all child NgModels below it
(unless a child has explicitly set its own value for this in ngModelOptions).
Potential values: 'change' | 'blur' | 'submit'
<form [ngFormOptions]="{updateOn: 'blur'}">
<input name="one" ngModel> <!-- this ngModel will update on blur -->
</form>
<form [ngFormOptions]="{updateOn: 'blur'}"><inputname="one"ngModel><!-- this ngModel will update on blur --></form>
As soon as you import the FormsModule, this directive becomes active by default on
all <form> tags. You don't need to add a special selector.
You can export the directive into a local template variable using ngForm as the key
(ex: #myForm="ngForm"). This is optional, but useful. Many properties from the underlying
FormGroup instance are duplicated on the directive itself, so a reference to it
will give you access to the aggregate value and validity status of the form, as well as
user interaction properties like dirty and touched.
To register child controls with the form, you'll want to use NgModel with a
name attribute. You can also use NgModelGroup if you'd like to create
sub-groups within the form.
You can listen to the directive's ngSubmit event to be notified when the user has
triggered a form submission. The ngSubmit event will be emitted with the original form
submission event.
In template driven forms, all <form> tags are automatically tagged as NgForm.
If you want to import the FormsModule but skip its usage in some forms,
for example, to use native HTML5 validation, you can add ngNoForm and the <form>
tags won't create an NgForm directive. In reactive forms, using ngNoForm is
unnecessary because the <form> tags are inert. In that case, you would
refrain from using the formGroup directive.