Feature Request: Introduce Concise Syntax for Defining Template Variables in Angular Templates about angular

[alxhub]

@DavidWeiss2 in this case I wouldn't recommend starting with a PR. There's a lot of complexity that goes into features like this, such as design reviews, potentially user studies, considerations of how it'll interact with future projects on our roadmap like signal components, etc. Your proposal for the syntax definitely contributes to the discussion, but I would hate for you to put in a lot of effort if that doesn't end up being the direction we go in.

[alxhub]

Closing as a duplicate of #15280.

[DavidWeiss2]

@alxhub
Is it ok I will create a PR with implementation of the mentioned suggestion? Or there is something need to be made before such a "big" change.

I see why you marked this as a duplicate, I will copy my suggestion to the mentioned issue.

Asking the above question here to have a quick ref to my suggestion. 😅

[DavidWeiss2]

@DavidWeiss2 in this case I wouldn't recommend starting with a PR. There's a lot of complexity that goes into features like this, such as design reviews, potentially user studies, considerations of how it'll interact with future projects on our roadmap like signal components, etc. Your proposal for the syntax definitely contributes to the discussion, but I would hate for you to put in a lot of effort if that doesn't end up being the direction we go in.

Thank you for the feedback.
Good points.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}