Wow, didn't even know you could do that.
LGTM

It's going to be hilarious when the babel people figure out this is a bug and the semicolon-free people need a semicolon remover.

Oh right, we need the same action for disallowSemicolons )

When prop without semicolon will became a valid syntax that is

Well when that happens it sounds like a good first bug/beginner friendly issue to me! 😄

@markelog It is already valid to omit semicolons after class properties in most cases.

@michaelficarra

Really?

semicolons are required always.

Really.

Don't see any clarification on the ASI in original link i provided, but judging by the interesting original discussion and rules of ASI you should be right.

Which means babel pr was indeed falsy (not this pr though) and that we can add same opposite logic to disallowSemicolons rule.

Thanks for playing!

You're welcome. Don't forget about this case which I hadn't thought of at first.

here’s the ASI clarification