Skip to content Skip to sidebar Skip to footer

Is There Anything Wrong With "move(-1)" As An Angularjs Expression?

I'm getting this error: [$parse:ueoe] Unexpected end of expression: move( From this code:

Solution 1:

I had the same thing. Check to make sure that it isn't one of your Chrome extensions that is causing the problem. I disabled Batarang specifically and the error went away.

Solution 2:

I'm facing the same problem and spent a few hours in it, but no luck. But hopefully my findings would be helpful.

The "bug" only happens on my main chrome windows, doesn't happen on incognito window, FF and IE.

In my case I tried to use: ng-click="changeScore(data.game.home, -1)", it reports ueoe. Tried to change to other arguments, but it doesn't work as long as it contains a dash:

changeScore(-1)
changeScore('-1')
changeScore('abc-efg')

When I step through angular.js, it seems like it has successfully parsed changeScore(data.game.home, -1) and then try to parse changeScore(data again, which is an incomplete statement, resulting error. But unfortunately I can't tell what has triggered the re-parse and can't reproduce it in jsfiddle.

Post a Comment for "Is There Anything Wrong With "move(-1)" As An Angularjs Expression?"