- directive in module ng
The ngController directive attaches a controller class to the view. This is a key aspect of how angular supports the principles behind the Model-View-Controller design pattern.
MVC components in angular:
- Model â Models are the properties of a scope; scopes are attached to the DOM where scope properties are accessed through bindings.
- View â The template (HTML with data bindings) that is rendered into the View.
- Controller â The
ngControllerdirective specifies a Controller class; the class contains business logic behind the application to decorate the scope with functions and values
Note that you can also attach controllers to the DOM by declaring it in a route definition via the $route service. A common mistake is to declare the controller again using ng-controller in the template itself. This will cause the controller to be attached and executed twice.
Directive Info
- This directive creates new scope.
- This directive executes at priority level 500.
Usage
- as attribute:
<ANY ng-controller="expression"> ... </ANY>
Arguments
| Param | Type | Details |
|---|---|---|
| ngController | expression | Name of a constructor function registered with the current $controllerProvider or an expression that on the current scope evaluates to a constructor function. The controller instance can be published into a scope property by specifying If the current |
Here is a simple form for editing user contact information. Adding, removing, clearing, and greeting are methods declared on the controller (see source tab). These methods can easily be called from the angular markup. Any changes to the data are automatically reflected in the View without the need for a manual update.
Two different declaration styles are included below:
- one binds methods and properties directly onto the controller using
this:ng-controller="SettingsController1 as settings" - one injects
$scopeinto the controller:ng-controller="SettingsController2"
The second option is more common in the Angular community, and is generally used in boilerplates and in this guide. However, there are advantages to binding properties directly to the controller and avoiding scope.
- Using
controller asmakes it obvious which controller you are accessing in the template when multiple controllers apply to an element. - If you are writing your controllers as classes you have easier access to the properties and methods, which will appear on the scope, from inside the controller code.
- Since there is always a
.in the bindings, you don't have to worry about prototypal inheritance masking primitives.
This example demonstrates the controller as syntax.
This example demonstrates the "attach to $scope" style of controller.
Please login to continue.