🐛 Parser doesn't throw an error about the duplicate private class member

[nissy-dev]

Environment information

I will share the playground link in the next section.

What happened?

Parser doesn't throw an error about the duplicate private class member.
The duplicate private class member raises the syntax error in runtime.

Playground Link

https://docs.rome.tools/playground/?indentStyle=space&quoteStyle=single&trailingComma=none&lintRules=all&enabledLinting=false&code=YwBsAGEAcwBzACAAQQAgAHsACgAgACAAIwBmAG8AbwA7AAoAIAAgACMAZgBvAG8AOwAKAH0ACgA%3D

https://docs.rome.tools/playground/?indentStyle=space&quoteStyle=single&trailingComma=none&lintRules=all&enabledLinting=false&code=YwBsAGEAcwBzACAAQQAgAHsACgAgACAAZwBlAHQAIAAjAGYAbwBvACgAKQAgAHsAfQAKACAAIAAjAGYAbwBvADsACgB9AAoA

Expected result

Prettier and TypeScript throw an error about the duplicate private class member. Rome also throw an error?

TypeScript Playground Link
https://www.typescriptlang.org/play?#code/MYGwhgzhAECC0G8BQ1oGIBmB7L0C80AjANwrra4EBMpAvkkA

Code of Conduct

• I agree to follow Rome's Code of Conduct

[ematipico]

This is a nice opportunity to create a new analyzer rule that checks that.

We already have an analyzer that check syntax errors: https://github.com/rome/tools/blob/main/crates/rome_js_analyze/src/syntax/nursery/no_super_without_extends.rs

[nissy-dev]

OK. I will update #4137 and the rule noDuplicateClassMembers will check duplicate private class members.

[ematipico]

OK. I will update #4137 and the rule noDuplicateClassMembers will check duplicate private class members.

Actually, that's not needed.

What I was suggesting was creating a NEW rule. That new rule will be a syntax rule, like the one I showed in my previous comment.

Those rules are particular: they don't have code actions and can't be turned off. These are rules that should check syntax or runtime errors

[nissy-dev]

Thank you for your explanation. I could understand. I will take this issue and create the new syntax rule.