Skip to content

Angular expressions should be plain TypeScript expressions #43485

@petebacondarwin

Description

@petebacondarwin

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:

  1. How close to ECMAScript syntax we want to stay
  2. What are the security implications of exposing particular syntaxes
  3. 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

  1. feat(compiler): Support "in" operator in Angular templates #38560
  2. Align with the optional chaining spec #34385
  3. Pipe (|) operator has incorrect precedence (too tight) #27415
  4. Support arrow functions in template syntax #14129
  5. Proposal: Allow computed property names in map expressions #13855
  6. Use the spread operator in template #11850
  7. Allow bigint literals in templates #44852

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: compilerIssues related to `ngc`, Angular's template compilercanonicalThis issue represents a canonical design issue in Angular.featureIssue that requests a new feature

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions