消化周期何时触发（如果有的话）？

Question

I have a small problem, I am using a route like

.when('/beta/profiles/new', {
  controller: 'ProfilesController',
  controllerAs: 'vm',
  templateUrl: 'profiles/new.html',
  resolve: {
    action: function() { return "new"; }
  }
})
.when('/beta/profiles/index', {
  controller: 'ProfilesController',
  controllerAs: 'vm',
  templateUrl: 'profiles/index.html',
  resolve: {
    action: function() { return "index"; }
  }
})

now in my controller I have something like this:

function ProfilesController(profileService, action) {
  var vm = this,
      permittedActions = ["index", "new"];
  var actions = {
    index: function() {
      vm.hideProfile = {
        currentProfile: null,
        showModal: false,
        setCurrentProfile: function(profile_id) { this.currentProfile = profile_id },
        toggleHide: function() {/*...*/}
      }
      profileService.all().then(function(data) {
        vm.profiles = data.result;
      })
    },
    new: {/*.. */}
  }
  if(permittedActions[action] > -1) actions[action]();
}

now my question is if I hit a link (in the header,lets say) multiple times in succession, each time I hit profiles/index.html should it re-initialize everything ?

if I want to takethe advantage of angular's dirty checking thing should I put the vm.hideProfile out of the index function ? and If I do that should I also not do the same with vm.profiles = [];?

how/what can I do to check if variables are getting re-initialized and angular's dirty checking is not in play, or is it just common sense!! or should I just have a separate controller for each action?

and in case of re-initialization, is there any better way so that I can keep the hideProiles inside the index because I really don't need my new and show actions to know about hideProfile , since its unnecessary?

Answer 1

A few things that hopefully can help:

1. Dirty checking is for objects bound to an active $scope (and $rootScope). https://docs.angularjs.org/guide/scope

2. To use $scope in your controller, (a) inject it. eg ProfilesController($scope, profileService, action), (b) put things on it, eg $scope.vm = vm;

3. looking at your code, the raw initialization should be super fast.

4. Don't think javascript is secure. If security is a real concern for your app, protect at the server.

Lastly on app arch, since angular is an MVC framework: define functions in your controller, and connect them to actions in the view via $scope. eg

$scope.index = function() { // do stuff 
  if (action !== "index") {return}; // disallowed by route
  //continue
}