Essentially every single web application being developed out there gets inputs from its users. Maybe it’s got a comment feed with a few text boxes. Or maybe it has some sort of calculator with different inputs and sliders. Of course, there’s almost always the login page. Yes, the email and password are inputs as well.
When working on web apps you’re going to be handling inputs quite a bit, and if so, you should be well equipped to use the right tools for the job. With AngularJS, those tools should include the extensive support for forms, inputs and validations.
I’ve covered the basics of writing forms before, but in this article I’d like to point out how Angular’s forms have a few magic properties that are worth knowing, since they can spare you some bugs and code!
First Things First: Getting Access to the Form
Forms in AngularJS have special properties, but how exactly are you meant to get access to these forms? The trick is to name the form. Once provide a name for your forms, AngularJS will automatically expose it under that name in your scope.
For example, say that we have this as part of the template of a component with
$ctrl as its controller-as name:
1 2 3
Setting the name to
$ctrl.exampleForm means that in the template we can get access to the form, simply by using
It can also be accessed from the controller’s code, using
Now that we know how to get access to the form, let’s start making use of it!
Testing Whether the User Has Interacted With the Form
A very common use case is the need to display certain error messages or help tips only after the user has started changing values in the form (or hasn’t started yet).
To do just that, forms in AngularJS come supplied with two handy boolean properties,
These two booleans are always the negative of the other (i.e.
$pristine === !$dirty).
When the form is in its virgin state and the user hasn’t changed anything yet,
$pristine is set to
Once the user has interacted with the form’s inputs,
$pristine is set to
$dirty is true.
In case you need to programmatically force the form back to its pristine state (e.g. the user clicked on reset, or after a successful save), you can call
Display Things After Form Submission
Sometimes, we want form validations to only be displayed after the user has clicked the save button, instead of changing as the user types or moves between fields.
In those cases, simply hiding validations until the form becomes
$dirty won’t do, which is exactly why forms also have the handy
This property gets set to
true once the user has submitted the form, even if the form is invalid.
Submitting a form means clicking a button that has the attribute
type="submit", or pressing Enter/Return inside an input.
AngularJS won’t prevent the form from being submitted if it’s invalid, meaning your
ng-submit callback is called.
You need to make sure not to act in case the form isn’t in a valid state.
Checking if the Form Is Valid
And just in order to check whether the form is valid or not, forms come equipped with a few more swanky properties.
First of all are the
true – go right ahead.
true – something is amiss.
In case the form is invalid, the form’s
$error hash will contain all the necessary information about which fields are invalid and for what validations.
But, there’s another state here, which is when both are
This is possible when the form has asynchronous validators.
This means that it’s important to test these are
false and not just “falsy” (e.g.
You can also check whether the form is currently pending, and see which of the validators are being processed, by accessing the
$pending hash (which is structured similarly to
There’s lots more that can be written about forms and their inputs in AngularJS, so if you’d like to hear more please subscribe below!
You want to do Angular the right way.
You hate spending time working on a project, only to find it’s completely wrong a month later.
But, as you try to get things right, you end up staring at the blinking cursor in your IDE, not sure what to type.
Every line of code you write means making decisions, and it’s paralyzing.
You look at blog posts, tutorials, videos, but each is a bit different.
Now you need to reverse engineer every advice to see what version of Angular it was written for, how updated it is, and whether it fits the current way of doing things.
What if you knew the Angular Way of doing things?
Imagine knocking down your tasks and spending your brain cycles on your product’s core.
Wouldn’t it be nice to know Angular like a second language?
You can write modern, clean and future-ready Angular right now.
Sign up below and get more of these helpful posts, free!
Always up to date and I’ve already done all the research for you.
And be the first the hear about my Modern Angular 1.x book – writing future proof Angular right now.