Semicolons become mandatory after a class property

[ChrisCinelli]

Babel 6.4 started reporting errors when a class property do not end in a semicolon.
jscs seems not even be bother that the semicolons are missing there.

In particular it would be great if --fix- could fix this problem since we now have hundreds of classes and almost all files are missing multiple semicolons.

See also http://stackoverflow.com/questions/35103415/autofix-babel-6-4-a-semicolon-is-required-after-a-class-property

[hzoo]

Yeah you can use the requireSemicolons rule for this.

[markelog]

@hzoo so we can close this, right?

[ChrisCinelli]

I am using atom-jscs. This is my .jscrc:

{
  "preset": "airbnb",
  "disallowSpacesInAnonymousFunctionExpression": null,
  "validateLineBreaks": "LF",
  "validateIndentation": 2,
  "excludeFiles": ["build/**", "node_modules/**"],
  "requireSemicolons" : true,
  "esnext": true,
  "validateQuoteMarks": null
}

Class properties without a semicolon are not highlighted with a linting error and not fixed.

[hzoo]

Did you update to jscs 2.9.0? It was added in that version

[ChrisCinelli]

No, I am using Atom-linter-jscs that apparently has not update yet.
See also : AtomLinter/linter-jscs#171 and https://github.com/AtomLinter/linter-jscs/commits/master/package.json

[hzoo]

You should be able to reinstall that package and it would have the latest dependency right? It's using ^ https://github.com/AtomLinter/linter-jscs/blob/master/package.json#L18

Either way you should be good to go when they update so goina close