Perfect! I was actually quite happy with the interpolation binding (fixing the identifier on each line) and had no idea it wasn't allowed!
Many thanks, M. . On Tue, 18 Jun 2019 at 19:45, Mike Jumper <[email protected]> wrote: > On Tue, Jun 18, 2019 at 11:14 AM Mark Nolan <[email protected]> wrote: > > > ... > > The browser console shows this: > > > > angular.js:14800 Error: [$parse:syntax] > > > > > http://errors.angularjs.org/1.6.9/$parse/syntax?p0=%7B&p1=invalid%20key&p2=17&p3=xxxAuthGcpStop(%7B%7Bitem.identifier%7D%7D)&p4=%7Bitem.identifier%7D%7D > > ) > > at angular.js:88 > > at q.throwError (angular.js:15358) > > at q.object (angular.js:15347) > > at q.primary (angular.js:15236) > > at q.unary (angular.js:15224) > > at q.multiplicative (angular.js:15211) > > at q.additive (angular.js:15202) > > at q.relational (angular.js:15193) > > at q.equality (angular.js:15184) > > at q.logicalAND (angular.js:15176) "<svg id="xxx-stop" width="100%" > > height="100%" viewBox="0 0 16 24" fit="" focusable="false" xmlns=" > > http://www.w3.org/2000/svg"; preserveAspectRatio="xMidYMid meet" > > class="xxx-icon xxx-enabled" > > ng-click="xxxAuthGcpStop({{item.identifier}})">" > > > > Did you mean: > > ng-click="xxxAuthGcpStop(item.identifier)" > > ? > > For AngularJS, depending on the directive, you'll find things like > some-attribute="{{ angular expression }}" and some-attribute="angular > expression". The ngClick directive is one of the latter. The double braces > introduce an angular expression, when necessary, but are not valid syntax > _within_ an angular expression. > > - Mike >
