Support UTF in Angular expressions
See original GitHub issueCurrently the lexer in change detection uses StringWrapper.charCodeAt()
- in Dart it returns
s.codeUnitAt()
which supports UTF - in JS it returns
str.charCodeAt()
which does not support UTF
Issue Analytics
- State:
- Created 9 years ago
- Reactions:9
- Comments:23 (7 by maintainers)
Top Results From Across the Web
Angular Expressions - W3Schools
AngularJS expressions do not support conditionals, loops, and exceptions, while JavaScript expressions do. AngularJS expressions support filters, while ...
Read more >How can I use special characters in angular directives ...
How can I use special characters in angular directives attributes? · javascript · angularjs · utf-8 · special-characters · directive.
Read more >Upgrading from AngularJS to Angular
This is a module that contains utilities for bootstrapping and managing hybrid applications that support both Angular and AngularJS code. When you use...
Read more >Top 40+ Angular Interview Questions and Answers for 2023
Angular supports four types of decorators, they are: ... Filters are used to format an expression and present it to the user.
Read more >Top 18 Most Common AngularJS Developer Mistakes - Toptal
Fortunately, ui-router supports that out of the box with absolute named view targeting. // A COMPLEX PRODUCT PAGE // WITH NO MORE TROUBLE...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’d like to see full UTF-8 support for properties in templates, too. Not every programmer speaks English, and as to my experience, it’s a good idea to use your native language for things like variable and method names. It helps to distinguish between your own entities and the entities defined by the framework. Usually, all the popular names are already reserved by frameworks 😃.
This issue is still relevant and it is confirmed bug in the latest version of Angular, see: https://stackblitz.com/edit/angular-ivy-nuc4uz?file=src/app/app.component.ts
tl;dr; is that it is all about making non-ASCII characters in Angular expressions: