Open phaneendra opened 8 years ago
:+1:
It seems to come from the esformatter-semicolons. If you desactivate it from the esformatter.json of the semi-standard module, after formatting you will not have the semicolons again.
I read some issues directly on esformatter-semicolons about it but i don't find anything to fix it :(
+1 for this issue
Cannot reproduce, has this been fixed by one of the dependencies or is it still an issue?
It's still here only after "MemberExpression".
The semi
package this project depends on has been deprecated. Should I fork and fix this @ricardofbarros
Sure @fabiosantoscode I will happily accept an PR 😃
$ node -v v4.2.2
$ npm ls semistandard-format -g /Users/phaneendra/.nvm/v4.2.2/lib ├─┬ semistandard@7.0.4 │ └── semistandard-format@1.6.7 └── semistandard-format@2.1.0
$ semistandard-format -v 2.1.0
formating causes additional semicolans to be added to jsx syntax
source
After formating
This causes an issue with sublime linter SublimeLinter: semistandard output: