I have a two-way data binding that is not altering the value of the variable sent to the directive.
My directive watches for a trigger and gives focus to the associates element (based on code found here at SO):
app.directive('focusMe', function ($timeout) {
return {
scope: {
trigger: '=focusMe'
},
link: function (scope, element, attrs) {
scope.$watch('trigger', function(value) {
console.log("directive value: " + value);
console.log("directive start: " + scope.trigger);
if (value === true) {
$timeout(function () {
element[0].focus();
scope.trigger = false;
console.log("directive end: " + scope.trigger);
});
}
});
}
}
});
In the HTML I call it as follows:
<input type="text" ng-model="item.value" focus-me="focusInput" />
When I trigger it for the first time, it works -- because the focusInput
variable switches its value. But focusInput
in the controllers scope (outside the directive) does not switch back to false
when the directive completes.
This switch back to false
should happen when I call scope.trigger = false
, assuming I understand what should be happening.
What is missing that would cause the two-way binding to not push the value back to the variable passed into the directive?
UPDATE 01:
For posting the question I removed a small bit of code. The HTML actually looks like this:
<input type="text" ng-model="item.value" focus-me="focusInput" ng-if="item.condition != 'matches' && item.condition != 'does not match'" />
If the input
fields hides and then is re-shown (based on the ng-if
) the directive will properly give focus the first time focusInput
changes. It will stop working again after that... unless the hide/show process is repeated.
AngularJS creates a two way data-binding between the select element and the $ctrl.
Two-way data binding can be achieved using a ngModel directive in Angular. The below syntax shows the data binding using (ngModel), which is basically the combination of both the square brackets of property binding and parentheses of the event binding.
A - ng-bind directive binds the AngularJS Application data to HTML tags.
Data binding is the most useful and powerful feature among any of the existing or upcoming software development technologies. It is actually a process that bridges a connection between the view and business logic of the application.
The problem you are experiencing is a common problem when dealing with primitive values (boolean, int, etc..) within scopes.
I strongly suggest reading Understanding Scopes article. (short answer: primitives are changed in the directive's isolated scope, and are not seeked up the chain for the parent scope, i.e., your controller scope).
As to how to solve your situation, I suggest to use dot notation and store your primitive inside an object, and bind this object to your directive:
scope: {
triggerObj: '=focusMe'
},
And make sure your trigger references in the directive are now scope.triggerObj.trigger
.
And in your controller have:
$scope.triggerObj = {};
$scope.triggerObj.trigger = true; //or false, what have you
Having an object will make sure the two way binding will work. And read the article above when you have time :)
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