I think you are probably using a child scope and don’t know it. ng-if, ng-repeat, ng-switch and ng-include all create child scopes. Values on your scope are inherited, but if you change the value in a child scope it sets a value on the child scope and leaves the inherited value unchanged on the parent. … Read more
You can’t bootstrap a module inside another bootstrapped module. Bootstrapping compiles the view and binds a rootScope to it, traversing it’s way through the DOM and setting up scope bindings and executing directive linking functions all the way through. If you do that twice, you’re going to run into problems. You’re probably going to have … Read more
Since you are sending the target element to your function, you could do this to get the id: function doStuff(item){ var id = item.attributes[‘data-id’].value; // 345 }
Since both functions are in the same scope you can simply call $scope.fn1() inside fn2.
$rootScope var which points to the parent of all the scopes and can be injected everywhere. All other scopes are children of the $rootScope. They are created via the $new method of the $rootScope thus every scope inherits from the $rootScope. In the angular source in the definition of the Scope constructor there is a … Read more
$watch() will be triggered by: $scope.myArray = []; $scope.myArray = null; $scope.myArray = someOtherArray; $watchCollection() will be triggered by everything above AND: $scope.myArray.push({}); // add element $scope.myArray.splice(0, 1); // remove element $scope.myArray[0] = {}; // assign index to different value $watch(…, true) will be triggered by EVERYTHING above AND: $scope.myArray[0].someProperty = “someValue”; JUST ONE MORE … Read more
All watches are evaluated (sometimes multiple times) every digest loop. The digest loop is entered as a result of some event, or calling $apply(). Watches are not called periodically based on a timer. See https://docs.angularjs.org/guide/scope#integration-with-the-browser-event-loop The browser’s event-loop waits for an event to arrive. The event’s callback gets executed… Once the callback executes, the browser … Read more
Angular 2.0 is using this instead of $scope. One of the major changes coming in 2.0 is the death of the controller, and a new emphasis on components. Big advantage of moving towards component-based apps is that it’s easier to define their interfaces; plus, HTML elements already have an easily mappable interface in events, attributes, … Read more
You can do this way: {{$root.rsLabels.welcome}}
Can you try just using $scope.$on()? Every time controller A is created, it is adding a new listener on the root scope, and that doesn’t get destroyed when you navigate away and back. If you do it on the controller’s local scope, the listener should get removed when you navigate away and your scope gets … Read more