Angular 1.3 brings a new directive called "ng-model-options." You can see I have a form here, with an input, and that has an ng-model-options. That is pointing to an object I have on this view model, called "modelOptions," and that's right here.
Let's go ahead and hide this HTML really quick. There are a couple of properties that go into ng-model-options, and I'm going to talk about two of those in this video. The first is updateOn, and that's a string.
You can say, "Update on the default," and that will be the default behavior. Hello@gmail.com. It's just what we've all come to know and love. You can also have blur. Instead, you say, "firstname.lastname@example.org," and then the model doesn't get updated until the input is blurred.
You can put all kinds of event names in here. You can have keyup. You can have keydown. Where this comes in really handy is with the other thing that we want to talk about. Let's just switch this to the default.
One other thing. You can have multiple event listeners in here as well. You have blur and default, separated by a space, and the model will be updated on both of those events.
Now, if we add debounce...If you're familiar with the concept in general, you'll know that we're telling Angular to wait before doing something if that something is called over and over again.
Basically, when we say "Debounce 500," that's saying, "Hey, Angular, don't update my model until 500 milliseconds after the last time I told you to update it." That allows us to do a lot of cool things.
If we were doing asynchronous searching, we want to give the user some time to type what they're actually trying to type before we actually hit the server. Let's just see what this looks like, If I say, "email@example.com," boom. It doesn't get updated immediately.
Where this comes in handy with updateOn is we add it as an object instead. Whoops. Now, the keys of this object are the events, and the values are how long we want the debounce to be for that event.
If we say "Default to be 1500," as they're typing, we want these things to be updated every second and a half. Blur is zero. We don't want it to debounce on blur. Then you get this kind of effect.
Let's say, "firstname.lastname@example.org." That was our default, and it updated after a second and a half. If I'm a user who knows what they're typing and moves on to the next input field, then I can say...Let's let that update..."email@example.com."
Then I move onto the next. I blur, and that bound value gets updated immediately. This is very powerful for validation, for asynchronous operations, all kinds of things. This is definitely a feature that I will be using very frequently.
All that you need to do is have this ng-model-options directive, give it an object with these keys on it, and you'll get that just baked in. This is something that you can still do with Angular 1.2, but it's really handy to have it built into the Angular core with 1.3