Author: Andreas Plahn

This is where one-time bindings come in. So what are one-time bindings? Let’s just read what the official docs say:One-time expressions will stop recalculating once they are stable, which happens after the first digest…And this is exactly what the Angular world needs to tackle the problems mentioned above. So what does it look like when we want to use one-time binding? Angular 1.3 comes with a new syntax for interpolation directives and expressions in order to tell Angular that this particular interpolated value should be bound one-time.Using this new syntax is as easy as starting an expression with ::. So if we apply the one-time expression to our example above, we change this:Hello {{name}}!To this:Hello {{::name}}!This works for all kind of typical Angular expressions you’re used to use throughout your app. Which means you can use them in ng-repeat expressions or even for directives that expose attributes that set up a two-way binding from the inside out. From the outside you’re able to just feed them with a one-time expression:

Source: One-time bindings in Angular 1.3

Show hide elements in AngularJs html template based on if $scope variable has value: (the ng-show=model.property is the trick)

    <li class="List-item" ng-repeat="row in searchResult">
        <div class="List-itemBody">
            <strong ng-show="row.doc.ContactPerson">{{row.doc.ContactPerson}}</strong>
            <strong ng-show="row.doc.ContactPerson == null">[Contact Person Missing]</strong>