ng-book

Filters 49
formName.inputfieldName.$error
If a validation fails, then this property will be true; if it is false, then the value has passed the input
field.
A Little Style Never Hurts
When AngularJS is handling a form, it adds specific classes to the form based upon the current state
of the form (i.e. if it’s currently valid, unchanged, etc.). These classes are named similarly to the
properties that we can check, as well.
These classes are:
.ng-pristine {}
.ng-dirty {}
.ng-valid {}
.ng-invalid {}
They correspond to their counterpart on the particular input field.
When a field is invalid, the .ng-invalid class will be applied to the field. This particular site sets
the CSS class as:
input.ng-invalid {
border: 1px solid red;
}
input.ng-valid {
border: 1px solid green;
}
$parsers
When our user interacts with the controller and the $setViewValue() method has been called on
the ngModelController, the array of $parsers functions are called as a pipeline. The first $parser
is called and passes its value to the next, and so on and so forth.
These functions have the opportunity to convert the value and change the validity state of the control
by using the $setValidity() functions.
Using the $parsers array is one way we can create a custom validation. For instance, let’s say we
want to confirm a value is between two numbers. We’ll push a new function on the $parsers array
that is called in the validation chain.
The value that we return from this $parser function is the value that will be passed down the chain
to the next parser. We return undefined if we don’t want the model to update.