Is it wrong using {{}} in AngualrJS directives?

Asked Dec 11 '15 at 08:59

Active Dec 11 '15 at 09:14

Viewed 119 times

This is how my code looks like:

<a href class="item" ng-repeat="area in subAreas"
    ng-click="house.cityId='{{ area.id }}';house.cityType='{{ area.type }}';loadMainList(house)">
       {{ area.name }}
</a>

But when I click this link on page and it's not working. There's no error message found in console, just no response. I inspected the element in Chrome, and the value passed correctly.

Finally, I tried to use the real values instead of {{...}} syntax, just for standard usage, like this ng-click="house.cityId=area.id;house.cityType=area.type;loadMainList(house)", the miracle happened, it worked. But this makes me confused as well.

Can anyone help explain what's the difference between these two usages? Or is it wrong using {{}} in AngularJS directives? I'm just a beginner in AngualarJS. Thanks in advance.

edited Dec 11 '15 at 09:14

asked Dec 11 '15 at 08:59

Sky

7,343
8
31
42

2

you do not need {{}} inside ng-click. – Tarun Dugar Dec 11 '15 at 09:01
1

`ng-click` already evaluates the content-string as an expression. So you don't need to tell to the framework that this is an expression as you would do with `{{}}` – Raulucco Dec 11 '15 at 09:05
Is that wrong using {{}} in angular directives? – Sky Dec 11 '15 at 09:13

Is it wrong using {{}} in AngualrJS directives?

0 Answers0