I'm trying to figure out why I'm having trouble overwriting a value passed to an angularJS directive via an isolate scope (@
). I try to overwrite the value of vm.index
with the following:
vm.index = parseInt(vm.index, 10)
However, it doesn't work for some reason.
If I change it to:
vm.newIndex = parseInt(vm.index, 10)
It works. Also, assigning the value on the $scope
works.
Why doesn't the first method work?
I've created this example plunker for reference.
As you used @
here which need value from an attribute with {{}}
interpolation directive. And seems like directive is getting loaded first & then the vm.index
value is getting evaluated. So the changes are not occurring in current digest cycle. If you want those to be reflected you need to run digest cycle in safer way using $timeout.
$timeout(function(){
vm.index = parseInt(vm.index, 10)
})
Above thing is ensuring that value is converted to decimal value. The addition will occur on the on the directive html <h2>Item {{ vm.index + 1 }}</h2>
Working Demo
As per @dsfq & my discussion we went through the angular $compile
API, & found that their is one method call initializeDirectiveBindings
which gets call only when we use controllerAs
in directive with an isolated scope. In this function there are switch cases for the various binding @
,=
and &
, so as you are using @
which means one way binding following switch case code gets called.
Code
case '@':
if (!optional && !hasOwnProperty.call(attrs, attrName)) {
destination[scopeName] = attrs[attrName] = void 0;
}
attrs.$observe(attrName, function(value) {
if (isString(value)) {
destination[scopeName] = value;
}
});
attrs.$$observers[attrName].$$scope = scope;
if (isString(attrs[attrName])) {
// If the attribute has been provided then we trigger an interpolation to ensure
// the value is there for use in the link fn
destination[scopeName] = $interpolate(attrs[attrName])(scope);
}
break;
In above code you can clear see that there they placed attrs.$observe
which is one sort of watcher which is generally used when value is with interpolation like in our case it is the same {{index}}
, this means that this $observe
gets evaluated when digest cycle run, That's why you need to put $timeout
while making index
value as decimal
.
The reason @dsfq answer works because he use =
provides two way binding which code is not putting watcher directly fetching value from the isolated scope, here is the code. So without digest cycle that value is getting updated.
Apparently it has something to do with one-way binding of the scope index
value. So Angular won't update scope.index
(or this.index
in case of bindToController: true
) because scope is configured as
scope: {
index: '@'
},
If you change it to two-way binding like:
scope: {
index: '='
},
It will work:
<some-directive index="$index"></some-directive>
Demo: http://plnkr.co/edit/kq16cpk7gyw8IE7HiaQL?p=preview
UPD. @pankajparkar made a good point that updating value in the next digest fixed the issue. This approach for the problem then is closer then what I did in this answer.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With