I found this in AngularJS style guide
Prefer using controller as syntax and capture this using a variable:
That means that I can
when should I use $scope at all if I'm not interested in accessing anything in the $rootScope?
$scope is not just for accessing to properties or functions in the $rootScope. Example (not too often, by the way): Suppose you need to update a DOM element not in the angular way, it means updating it through any external library which modifies the component value (visually), but the ng-model of the component doesn't get updated and you need it to! What to do? Simple: $scope.$digest (depending on what you do, there might be any other angular function required).should I move everything to controller's this?
angular
.module('myapp', [])
.controller('foo', function() {
var vm = this;
// only this will be available in the view thanks to the controller as syntax
vm.wizard = {
userID: null,
totalCartCount: 0
}
// stuff used only inside the controller
vm.private = {
subtotalByProducts: [],
readyToCheckoout
}
// only "public" stuff is returned here
return vm.wizard;
// functions
});
If not, then what should stay in the $scope?
What you put in your $scope is completely up to you, as it is using the controller as syntax, but keep in mind that everything in the $scope is accessible in the view. The idea is to reduce the amount of variables passed to the view. This could not be noticeable in small webapp, but when the size of the app gets greater you can notice some changes (more time loading, etc).
This is a matter of perspective of each developer and how fond could be any of us of using best practices.