$scope.getNameLog = function () {
console.log('getting name');
return $scope.name;
};
<div ng-show="false">
<span></span>
</div>
function update() {
element.text(dateFilter(new Date(), 'hh:mm:ss'));
$timeout(update, 1000, false);
}
$scope.user = {
firstName: 'AngularJS',
lastName: 'Superhero',
age: 4,
superpowers: 'unlimited',
// many other properties go here…
};
$scope.$watch('user', function (changedUser) {
$scope.fullName =
changedUser.firstName + ' ' + changedUser.lastName;
}, true);
<p>This is very long text that refers to one defined on a
scope. This text can be really, really long and occupy a lot of space
in memory. It is so long since… </p>
--->
<p>This is very long text that refers to one <span ngbind='
variable'></span> defined on a scope. This text can be really,
really long and occupy a lot of space in memory. It is so long since…
</p>
its performance is linked to the size
of a collection
Collections of over 500
rows are probably a bad fit for the ngrepeat directive.