Angular controllers expressed as ordinary Javascript functions

Question

I've been looking at a lot of Angular tutorials online, and I'm seeing some inconsistencies in the way that AngularJS controllers are defined.

Most examples use a "chaining" syntax when instantiating controllers:

var myApp = angular.module('myApp', []).controller('FooCtrl', function() {
    // $scope.foo = ...
});

// alternatively:

var myApp = angular.module('myApp', []);
myApp.controller = function($scope, fooBar) {
    // $scope.foo = ...
}

In other examples I've seen, controllers are defined like you would define an ordinary Javascript function. I think I've encountered this approach in more than one tutorial!

var myApp = angular.module('myApp', []);

function FooCtrl($scope, fooBar) {
    // $scope.foo = fooBar ...
});

What's the difference between these two declarations?
Is the second example simply deprecated?
If not, then how does this Controller work with Angular's $digest cycle?

1st one is cool modularize approach..avoiding global function controller declaration — Pankaj Parkar, Mar 02 '15 at 18:50
@tymeJV It looks like the second example was deprecated with the release of AngularJS 1.2. Please post your comment as an answer and I will mark it as accepted! — alex, Mar 02 '15 at 19:49

score 0 · Accepted Answer · answered Mar 06 '15 at 19:14

0

Looks like the

function FooCtrl($scope, fooBar) {
    // $scope.foo = fooBar ...
});

function has been deprecated since the release of Angular 1.2.

answered Mar 06 '15 at 19:14

alex

6,818
9
52
103

Angular controllers expressed as ordinary Javascript functions

1 Answers1