Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Translate filter incorrectly assumes this===scope
See original GitHub issueSubject of the issue
When using the translate filter with a string argument, the filter uses $parse to parse the string, then evaluates the expression against this, assuming this is the current scope. But that is an incorrect assumption since Angular 1.3, see this commit:
https://github.com/angular/angular.js/commit/8863b9d04c722b278fa93c5d66ad1e578ad6eb1f
Your environment
- version of angular-translate: 2.9.0
- version of angular: 1.5.0
- which browser and its version: Chrome 53
Steps to reproduce
Example: https://plnkr.co/edit/vBoO2V?p=preview
(The example show the non-working string-parse case and contrasts with the working object case.)
Expected behaviour
Since it’s not possible to evaluate the parsed string against the scope, the filter should probably throw an exception.
Actual behaviour
The parsed string is evaluated against this, which is undefined, which means that scope variables are not resolved.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sure, I’ll fix!
5cb94cb