Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upstandard gets confused with es6 getter/setter #316
Comments
This comment has been minimized.
This comment has been minimized.
nekolab
commented
Nov 25, 2015
|
Hi, I ran into this issue too, it's annoying, any updates? |
This comment has been minimized.
This comment has been minimized.
|
Its an issue with standard-format and not standard (which just does the linting). ES6 support on the formatter is poor at the moment. PRs and new contributors welcome/wanted! @diasdavid if you have time can you move this issue over there? If not I can grab it later. I've only had time to peck away at it slowly, and there are definitely going to be some upstream PRs needed to get full ES6 support. |
This comment has been minimized.
This comment has been minimized.
|
Moved this issue: maxogden/standard-format#138 |
feross
closed this
Dec 25, 2015
lock
bot
locked as resolved and limited conversation to collaborators
May 10, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
daviddias commentedNov 4, 2015
It seems that when
standard --formatcatches a es6 getter/setter, it changes its format and than reports a codestyle error, see example belowThe right space was there, but then
Fixing the problem and running
standardreturns no errors, but then ifstandard --formatis executed, it will remove the space again and report an error