react-prefer-private-members should be typescript-only

[BPScott]

Currently running this rule reports violations in JS files, where it is not possible to define private members.

Can we run it only on files where it can actually be fixed - i.e. only typescript files?

[cartogram]

@BPScott You should be able to accomplish this with configuration in your project. https://eslint.org/docs/user-guide/configuring#example-configuration

Won't private properties be in JS eventually?

[BPScott]

There's a spec for it, but it's not yet fully implemented in babel - it's close though.

See https://babeljs.io/blog/2019/03/19/7.4.0#static-private-methods-9446-https-githubcom-babel-babel-pull-9446 for what the syntax looks like and what work has been done.

I can prefix my method with # but it currently throws a parser error as babel-eslint isn't setup to handle that (which should be fixed in babel-eslint 11 when they start reading from your local babel config (except we'll have to do some work because we insist on disabling usage ob babel.config.js) but that's not released yet.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.