feat(rome_js_analyze): noConstEnum

[Conaclos]

Summary

This is an exclusive rule for Rome!
This rule disallows TypeScript const enums.

Const enums pitfalls are described on TS docs.

See my comment for more context.

Test Plan

Unit test and doc-tests.

[netlify]

✅ Deploy Preview for docs-rometools canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	51f8d48
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rometools/deploys/63812e6ee7f6e00008cddfef

[ematipico]

The const enum is well reported with lintdoc (cf generated rule web page). However, it is not reported in unit tests. Any idea why?

No idea to be honest. First time I see this kind of issue. You could copy the snippet inside the quick_test we have inside rome_js_analyze/lib.rs and see if you get some output (it's ignored in purpose, you can remove the directive, test it, and put the directive again).

[Conaclos]

No idea to be honest. First time I see this kind of issue. You could copy the snippet inside the quick_test we have inside rome_js_analyze/lib.rs and see if you get some output (it's ignored in purpose, you can remove the directive, test it, and put the directive again).

Thanks for the hint. I misnamed the test: no_const_enum.ts instead of noCOnstEnum.ts. It could be nice to fail if a file does not match a rule name.