I have one concern when creating a custom directive in angular. When I'm using a link function, I'm not sure what is the real difference when accessing attributes with attrs or scope. Take this piece of code for example:
myApp.directive('someDirective', function() {
return {
restrict: 'E',
replace: true,
scope: {
title: '=title'
},
template: '<img/>',
link: function(scope, element, attrs) {
if (scope.title) {
// do something here
}
if (attrs.title){
// do something here
}
},
}
From my observations accessing 'title' attribute from attrs and by scope has a similar effect. What is the real difference?
I have one concern when creating a custom directive in angular. When I'm using a link function, I'm not sure what is the real difference when accessing attributes with attrs or scope. Take this piece of code for example:
myApp.directive('someDirective', function() {
return {
restrict: 'E',
replace: true,
scope: {
title: '=title'
},
template: '<img/>',
link: function(scope, element, attrs) {
if (scope.title) {
// do something here
}
if (attrs.title){
// do something here
}
},
}
From my observations accessing 'title' attribute from attrs and by scope has a similar effect. What is the real difference?
Share Improve this question edited Oct 2, 2017 at 23:23 NOCARRIER 2,6345 gold badges42 silver badges62 bronze badges asked Jun 22, 2015 at 19:47 Marcin86Marcin86 1312 silver badges9 bronze badges 1- Please look at this stackoverflow./questions/14300986/… – michelem Commented Jun 22, 2015 at 19:53
1 Answer
Reset to default 20The difference is that attribute is of a String type by definition. Always. In your case attrs.title
will be literally string equal to whatever you pass into attribute in HTML.
However, scope.title
is parsed and evaluated result of the attribute attr.title
.
Ex. If you use something like this in HTML
<some-directive title="name"></some-directive>
where $scope.name = "Thomas Mann"
defined in the scope, then attr.title
will be string "name"
, while scope.title
will be "Thomas Mann"
.