'=' (expression) scope attributes use !== instead of angular.equals to compare

[Martin Probst]

Hi,

the new scope bindings in Angular 1.0 use !== to compare for equality, instead of angular.equals.

This means if you have any binding that constructs new objects as part of its computation, you'll run into the max $digest TTL issue.

Is this by design? The code we had before was working fine with accessor bindings (and it still looks to work fine, it's just one empty array that keeps the $digest spinning).

Martin

[ste...@sock.org.uk]

Hi Martin

If I've understood your question correctly, you just need to pass 'true' as the third parameter (objectEquality) in your calls to $watch [1] - this will ensure that calls to $digest use angular.equals [2].

I'm afraid I can't answer as to whether this is by design - I just know that it confused me a bit last week!

Stephen

[1] https://github.com/angular/angular.js/blob/master/src/ng/rootScope.js#L284

[2] https://github.com/angular/angular.js/blob/master/src/ng/rootScope.js#L395

[Martin Probst]

If I've understood your question correctly, you just need to pass 'true' as the third parameter (objectEquality) in your calls to $watch [1] - this will ensure that calls to $digest use angular.equals [2].

I know, but this is actually set up by Angular itself, when setting up bindings for directives with scope: { foo: '=' }. So I have no chance of fixing this.

Martin

[ste...@sock.org.uk]

If I've understood your question correctly, you just need to pass 'true' as the third parameter (objectEquality) in your calls to $watch [1] - this will ensure that calls to $digest use angular.equals [2].

I know, but this is actually set up by Angular itself, when setting up bindings for directives with scope: { foo: '=' }. So I have no chance of fixing this.

In that case all I can do is agree with you that the new behaviour feels like a regression (but I'm quite new to angular so I'll expect to be proved wrong).

Stephen