The 'controller as' technique for AngularJS was described by John Papa as:
myApp.controller("MainCtrl", [
function () {
var vm = this; // convention - ViewModel
vm.person = { name: "Bob" };
return vm;
}]);
What is the purpose of the return vm;
line? The code works without it.
The 'controller as' technique for AngularJS was described by John Papa as:
myApp.controller("MainCtrl", [
function () {
var vm = this; // convention - ViewModel
vm.person = { name: "Bob" };
return vm;
}]);
What is the purpose of the return vm;
line? The code works without it.
- From my POV vm is returned to produce a chained method – Dalorzo Commented May 26, 2014 at 21:17
-
1
I don't think it has anything to do with chained methods (but I've been wrong before) and I don't see how it changes the default behaviour (which is to return
this
). – gkalpak Commented May 26, 2014 at 21:38 - 1 To quote the author of the article: "That’s just my convention" – a better oliver Commented May 27, 2014 at 12:04
1 Answer
Reset to default 6When Angular is creating your controller, it will use the new
keyword on the function you passed in. Thus, it will construct a new object using the constructor you passed in. Returning objects from your constructor function will cause the Angular to use that instance of your newly created object as with any other use of a JavaScript constructor.
There are some details about the constructing process (see this SO answer) to keep in mind:
- When the returned object is the same as
this
it can be omitted, asthis
will be used by default. - If returning some primitive type or
null
(essentially anything that'snull
or not anObject
, as described in the SO answer linked to earlier),this
will be utilized as well. - If returning an instance, the reference to this instance will be returned.
Saying this
will be used in 1 & 2 is a trivial oversimplification. Again, see this answer regarding construction for specific details.
发布者:admin,转转请注明出处:http://www.yc00.com/questions/1742412814a4439157.html
评论列表(0条)