Repository navigation
Angular expressions should be plain TypeScript expressions #43485
Description
Which @angular/* package(s) are relevant/releated to the feature request?
compiler
Description
This issue is a container for all the issues that have requested new expression syntax features.
The aim is to collect all the features into one place so that we can track the work.
The plan is to do an holistic analysis of the syntax and decide things like:
- How close to ECMAScript syntax we want to stay
- What are the security implications of exposing particular syntaxes
- How to incorporate Angular specific syntax, such as pipes and structural directive microsyntax.
The result will be a project proposal for the changes that we would like to make to the syntax in the short to medium term.
Related Issues
- feat(compiler): Support "in" operator in Angular templates #38560
- Align with the optional chaining spec #34385
- Pipe (
|) operator has incorrect precedence (too tight) #27415 - Support arrow functions in template syntax #14129
- Proposal: Allow computed property names in map expressions #13855
- Use the spread operator in template #11850
- Allow bigint literals in templates #44852
Reacted by Andrew Kushnir, Xucong Zhan, Front-end developer, Ingo Bürk, Harpush, Lars Gyrup Brink Nielsen, Максим Иванов, Samuel Fernández, Chellappan, Sumit Parakh and 118 more
Reacted by Domas Trijonis, Dmitrii Kuzmin, Sadiinso, Rafael Santana, hiepxanh, Vlad Dumbrava, Vinit Neogi, Rodrigo Alves, Clara Castillo, Minko Gechev and 4 more
Reacted by Maksim Popov, antischematic, Rafael Santana, Enea Jahollari, Indraraj, Andrew Kushnir, Front-end developer, Максим Иванов, Minijus L, Daniel Marin and 41 more
Reacted by Oleksandr Voloshyn, Minijus L, Rafael Mestre, AwesomeObserver, Alfonso Andrés López Molina, Toni Villena, LanderBeeuwsaert, Oscar Busk, Matheus Ravanello Mokwa, HK and 13 more
Activity
samuelfernandez commentedon Oct 16, 2021
Could this enhancement for the compiler be included too? #43253
JoostK commentedon Oct 16, 2021
That appears to be unrelated to Angular's expression syntax, as it's a request for more accurate type-checking. So we'll keep that one separate.
RobertAKARobin commentedon Feb 11, 2022
Really looking forward to seeing this completed! Not having
as local-val, and having instead to use*ngIf, is a big turn-off for developers considering Angular or ramping up on Angular projects.[-]feat(compiler): improvements to the Angular expression syntax[/-][+]Angular expressions should be plain TypeScript expressions[/+]JeanMeche commentedon Jan 3, 2026
Update on some syntax improvements that will soon land: