Rule Suggestion: Require semicolon after class static properties

[IanVS]

Static class properties require a semicolon, as pointed out in https://phabricator.babeljs.io/T6873. Babel is now bombing with a compilation error if it doesn't find a semicolon. It would be super beneficial to have a linting rule to catch this.

[oztune]

+1

[hzoo]

We're goina revert to previous behavior since they discussed this more in tc39/proposal-class-public-fields#26 (comment)

babel/babel#3332

[IanVS]

Might still be nice to have a linting rule to enforce them, yes?

[hzoo]

Yeah, either way yes for users that wan't semicolons

[Download]

We're goina revert to previous behavior

Thanks!!! I hated having to add semicolons to all my source files! ... not sure if I'm going to revert them all but at least I can write the 'cleaner' semicolon-less version again now. Yay!!

[IanVS]

@Download, off-topic for this issue, but if you want to remove them, you can probably use ESLint's --fix

[ghost]

Do we still haven't got such a rule? Would be nice to have one.

+1

[mjrussell]

This would still be a great feature (both static and regular class properties) for those who enforce JS with semicolons.

+1

[jquense]

so the only way such a rule would make sense here is as an extension of the builtin semi rule that last enforces them in this case. if anyone wants to PR that I'd happily accept

[jeffshaver]

Would also like the option to disallow them unless necessary.

[elodszopos]

Hey guys, kind of an old thread. Anything going on with this one? Would be amazing to have this.

[r3nya]

Yeah! @elodszopos +1