Replies: 1 comment 1 reply
-
|
Being able to lint Angular templates requires an AST to be produced from Angular flavored HTML. I think it's very unlikely that oxc will be supporting parsing Angular flavored HTML any time soon, so at most you would only be able to port the rules that run on TS constructs, but not anything from I am very excited by oxc, but angular-eslint is one of the last projects that can be ported because of its need for a custom parser for non-JS(X)/TS(X) concerns. |
Beta Was this translation helpful? Give feedback.
-
|
If this is something you are passionate about seeing, maybe you can lead the charge for oxc to support pluggability in its parser, so that a relevant rust implementation could be written for turning an Angular Template to an appropriate AST. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Looks like https://github.com/oxc-project/oxc will be next default linter. That linter lint my 90 libs huge workspace for 1 sec instead of many minutes of eslint. According to support for many rules added oxc-project/oxc#481
Have you plans to port / support @angular-eslint and @angular-eslint/template rules to oxlint?
Beta Was this translation helpful? Give feedback.
All reactions