I am showing reactive form error messages as per the suggested approach of angular angular form validation error example.
html code of showing error on the page:
<div [formGroup]="myForm">
<div>
<input type="text" formControlName="firstName"/>
<div *ngIf="myForm.controls.firstName.invalid"
class="alert alert-danger">
<div *ngIf="myForm.controls.firstName.errors.required">
This Field is Required.
</div>
<div *ngIf="myForm.controls.firstName.errors.maxlength">
your can enter only 50 characters
</div>
</div>
</div>
<div>
<input type="text" formControlName="lastName"/>
<div *ngIf="myForm.controls.lastName.invalid"
class="alert alert-danger">
<div *ngIf="myForm.controls.lastName.errors.required">
This Field is Required.
</div>
<div *ngIf="myForm.controls.lastName.errors.maxlength">
your can enter only 50 characters
</div>
</div>
</div>
</div>
Just for the reference of my component code below :
this.myForm = this.formBuilder.group({
firstName:['',[Validators.required,Validators.maxLength(50)]],
lastName:['',[Validators.required,Validators.maxLength(50)]]
})
If you see the above code, I have applied two validation on my firstName and lastName field.
For showing error message, I have written multiple *ngIf condition to show the error message.
Is there any best way to show the validation message of particular control without writing multiple *ngIf condition ?, because the same code I am writing again and again with different control name and validator name for showing error message.
I would suggest to have a component called print-error which can handle any kind of OOTB or Custom errors.
You can handle as many as errors you want.
print-error.component.ts
import {Component, Input} from '@angular/core';
@Component({
selector: 'print-error',
templateUrl: './print-error.component.html',
providers: []
})
export class PrintError {
@Input("control")
control: any;
}
print-error.component.html
<div class="text-danger" *ngIf="control && control.errors && (control.dirty || control.touched)">
<div *ngIf="control.errors.required"><small>This field is required</small></div>
<div *ngIf="control.errors.unique"><small>{{control.errors.unique}}</small></div>
<div *ngIf="control.errors.lessThen"><small>{{control.errors.lessThen}}</small></div>
<div *ngIf="control.errors.greaterThan"><small>{{control.errors.greaterThan}}</small></div>
<div *ngIf="control.errors.email"><small>{{control.errors.email}}</small></div>
<div *ngIf="control.errors.mobile"><small>{{control.errors.mobile}}</small></div>
<div *ngIf="control.errors.confirmPassword"><small>{{control.errors.confirmPassword}}</small></div>
</div>
Usages
<label for="folder-name">Email</label>
<input name="email" required emailValidator #email="ngModel" [(ngModel)]="user.email">
<print-error [control]="email"></print-error>
I've been working on an enterprise application that is primary form driven and ran into the same challenge. The best solution I could determine was wrapping all of my input controls in components. Then handling the validation display within the component. This allows consistent validation display without repeating the code multiple times in each form.
field-input-text.component.html
<input [formControl]="formControlItem" [maxlength]="maxlength" [placeholder]="placeholder" #input>
<span *ngIf="formControlItem.invalid && (formControlItem.dirty || formControlItem.touched)" class="text-danger">
<span *ngIf="formControlItem.errors.required">This field is required</span>
<span *ngIf="formControlItem.errors.minlength">This field is too short</span>
<span *ngIf="formControlItem.errors.maxlength">This field is too long</span>
<span *ngIf="formControlItem.errors.pattern">Invalid value for this field</span>
</span>
field-input-text-component.ts
import { Component, OnInit } from '@angular/core';
import { FormControl } from '@angular/forms';
@Component({
selector: 'app-field-input-text',
templateUrl: './field-input-text.component.html'
})
export class FieldInputTextComponent implements OnInit, AfterViewInit {
@Input() formControlItem: FormControl;
@Input() maxlength: number;
@Input() placeholder: string = '';
constructor() { }
ngOnInit() {
}
}
Usage
<app-field-input-text [formControlItem]="form.controls.username" maxlength="10"></app-field-input-text>
In the usage, you can see the space it saves without needing the extra validation lines. You can also reformat all of the validation in one place instead of touching every area.
The main disadvantage is not being able to use the formControl or formControlName attributes. I tried creating a custom ControlValueAccessor component but that did not help with the validation display.
I found your question searching to see if anyone else have found a better way. I know this answer is a little late but hopefully it helps.
If it's a small form I usually just use lots of *ngIf; however, a custom validator directive as mentioned above might be useful if your application is almost entirely forms in need of validation.
Take a look at the source, to see how the built-in validators are set up.
https://github.com/angular/angular/blob/2.0.0-rc.3/modules/%40angular/common/src/forms-deprecated/directives/validators.ts#L104-L124
Here's an example I dug up, but I think it's a little overkill for most use cases. Just write an *ngIf line in the template HTML, instead of a whole new @Attribute...
https://scotch.io/tutorials/how-to-implement-a-custom-validator-directive-confirm-password-in-angular-2
I would suggest to have a directive and component to show powerfully error message.
component for each error message of form control and directive for add the component under the native element of form control.
the full code can be found here
