Controlling model input with ngModelOptions

This new helper directive introduces a new vector of control over model access and updating to the developer. Formerly, using ng-model bound to an input meant that validation or any verification of value change needed to happen in a controller helper method or in a scope watcher, neither of which ever felt very clean. With ngModelOptions, you are now able to make decisions about how and when the model will get updated.

Getting ready

The ngModelOptions directive will most directly benefit you while developing an AngularJS form, since it implicitly provides namespaces to the inputs within the form that are used by some of this directive's features. Suppose that for all the examples in this recipe, you begin, as follows:

<div ng-controller="PlayerCtrl">
  <form name="playerForm">
    Name:
    <input type="text"
           name="playerName"
           ng-model="player.name"
           ng-model-options="" />
  </form>
</div...