Angular 1.2: Using "terminal" on a directive breaks the interpolation on attrs.$observe

[portersi]

Here's an example using Angular 1.2 RC3:
http://plnkr.co/edit/LMF2YuJW1Opj9gS3wv63?p=preview

If you open the JS console you can see what the observed value is. It's uninterpolated with its curly braces still intact.

Here's the same code running on Angular 1.0.8 that works correctly:
http://plnkr.co/edit/E0vINw7Pyjk0G2I1UwBI?p=preview

[portersi]

I was playing around with priority and found that interpolation works with any priority less than -99. So with priority -100 the value is interpolated, with -99 it isn't. Not sure what's going on there...

[portersi]

Must be this:

angular.js/src/ng/compile.js

Line 1354 in 63c5334

priority: -100,

[portersi]

Maybe this isn't a bug? I can workaround by changing the priority, feel free to triage however you like.

[pschachner]

Having the same issue with last stable version (1.0.8). I have an expression with curly braces within ng-click directive, that makes the ng-click not to be called:

<button data-ng-click="redirectTo('employee/edit/{{employeeId}}' )">Edit</button>

[portersi]

This is a different issue. Attributes are generally either evaluated or interpolated -- ng-click is evaluated, not interpolated, so curly braces aren't treated special. You can try:

ng-click="redirectTo('employee/edit/' + employeeId)"

[btford]

I think this is working as intended. If you say a directive is terminal, and it has a higher priority than other directives on the same element, I would expect those directives not to be invoked by $compile. Like you said, you can specify a lower priority for your directive.