The caculateFunction(data.price) function will be called every time Angular runs change detection for the component (more precisely for the embedded view created by ngFor). This is because updating DOM is part of change detection and Angular needs to call caculateFunction to know what value to use for DOM update. And change detection cycle can run quite often. So if you have 3 items in the list and CD is triggered 3 times initially, you will see that the function is called 9 times.
If you inspect the updateRenderer function, you shoul see something along these lines:
function(_ck,_v) {
var _co = _v.component;
var currVal_0 = _co.calculateFunction(_v.context.$implicit);
_ck(_v,3,0,currVal_0);
}
Read more about how Angular updates DOM in The mechanics of DOM updates in Angular.
Should I worry about that for performance or just let angular2 do
this?
If calculateFunction(data.price) returns the same result for the same price, it’s better to calculate these values beforehand for each item and simply renderer them in the template.
<td>{{ data.no }}</td>
<td>{{ data.name }}</td>
<td>{{ data.calculatePrice) }}</t
In this way you will avoid performance decreasing function calls.