📎 Formatter should be able to handle Angular @Component decorators

[jpike88]

Description

See some example code from one of my Angular components.

Specifically, the template and styles properties in the @component decorator use HTML and CSS respectively. Rome Formatter should be aware of these specific properties (which are really the only two I know in common usage) and auto-format them accordingly.

Also, I noticed that selector and template properties don't get auto-indented. It's like Rome ignores everything in the decorator.

Prettier does this, by the way. So using Rome as a formatter will be a major problem for any Angular dev until the above case is handled

[xunilrj]

Thanks for the suggestion. We are starting to focus on specific demands of frameworks. We will definitely pay attention more to React, Vue, Svelte and Agular.

Although we don't have a hard deadline to give you about Angular.

It's like Rome ignores everything in the decorator.

Yes. That is what is happening. Unfortunately see #3197

So using Rome as a formatter will be a major problem for any Angular dev until the above case is handled

This is something that we definitely want to address.

[jpike88]

I am desperately struggling to use Rome instead of eslint, it's at a point where enabling eslint is vscode is causing crashes to occur:

microsoft/vscode#171691

The only real obstacle right now is that Rome doesn't recognised import statements as used when they're a decorator. As a stop gap, I would highly recommend doing the minimum as a priority, which is to parse decorator names so the import statements are considered 'used' in that file.