You can configure your own 1-way databinding behavior for booleans like this: link: function(scope, element, attrs) { attrs.$observe(‘collapsable’, function() { scope.collapsable = scope.$eval(attrs.collabsable); }); } Using $observe here means that your “watch” is only affected by the attribute changing and won’t be affected if you were to directly change the $scope.collapsable inside of your directive.
The reason is that since you’re creating an isolated scope for your contenteditable directive, the ng-model directive on the same element gets that isolated scope as well. Which means that you have two different scopes that aren’t connected to each other, which both have a form.userContent property that changes separately. I guess you could exemplify … Read more
You could use an Angular Service to share variable acrosss multiple controllers. angular.module(‘myApp’, []) .service(‘User’, function () { return {}; }) To share the data among independent controllers, Services can be used. Create a service with the data model that needs to be shared. Inject the service in the respective controllers. function ControllerA($scope, User) { … Read more
Although it’s not very sexy each dom node gets a class ng-scope so you could tech do something like this maybe: function getScope(id) { var elem; $(‘.ng-scope’).each(function(){ var s = angular.element(this).scope(), sid = s.$id; if(sid == id) { elem = this; return false; // stop looking at the rest } }); return elem; }
There are couple of ways to do register a callback once a digest is completed. Using $$postDigest: $scope.$$postDigest fires a callback after the current $digest cycle completed. However this runs only once after the next digest cycle. To make it run after each digest cycle run it along with $watch. This is based on the … Read more
Ah, obvious now…I can access the vm variable through making a reference to the controller that’s created in the test: it(“should assign Dashboard as title”, function () { var vm = controller(“dashboard”, { $scope: scope }); expect(vm.title).toBe(“Dashboard”); });
Your function is run 10 times. Why 10? Why not 100? The answer is in the docs: The watch listener may change the model, which may trigger other listeners to fire. This is achieved by rerunning the watchers until no changes are detected. The rerun iteration limit is 10 to prevent an infinite loop deadlock. … Read more
You question is not very clear, but if you declare controller using the module API, then you can provide the controller to the modal service as a string myApp.controller(‘ModalInstanceCtrl’, [‘$scope’, function($scope) { $scope.greeting = ‘Hola!’; }]); controller: ‘ModalInstanceCtrl’, The same can be done for loginCtrl if you want to use that in the modal service.
Although @user1737909 already referenced the SO question to read (What are the nuances of scope prototypal / prototypical inheritance in AngularJS?, which will explain the problem and recommended various ways to fix it), we normally try to give the answer on SO. So, the reason your fiddle doesn’t work is because when a primitive type … Read more
Directive ngRepeat creates a new scope for each iteration, so you need to reference your variables in parent scope. Use $parent.selected = value, as in: <p ng-repeat=”value in values” ng-click=’$parent.selected = value’>{{value}}</p> Note: Function call propagates due to prototypal inheritance. If you want to learn more: The Nuances of Scope Prototypal Inheritance.