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 --fix doesn't work sometimes #632
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
@dcposch Can you share the exact file (or better, a minimal example) that this bug happens on? Or is does it always happen for you on Windows? |
This comment has been minimized.
This comment has been minimized.
jacob-israel-turner
commented
Sep 21, 2016
|
|
feross
added
the
need more info
label
Sep 21, 2016
This comment has been minimized.
This comment has been minimized.
|
Without further information, this issue is really difficult to debug. @jacob-israel-turner How can you tell it's not working? Is the output indicating that there are automatically fixable errors and then you run Can you share the file and output from Other ideas:
|
This comment has been minimized.
This comment has been minimized.
mrchief
commented
Sep 22, 2016
|
It doesn't work on multiple runs. Removing the |
This comment has been minimized.
This comment has been minimized.
jacob-israel-turner
commented
Sep 22, 2016
•
|
@feross I would run I saw @Flet's comment about multiple errors on one line, so I went through and fixed all errors that were on a single line, and it seemed like Seems like there are just some situations where it thinks it can fix something for me, but in reality it can't. However, in the end, I didn't have to manually fix any beginning-of-line spacing, or remove any semicolons. So it definitely worked to an extent. EDIT: And I didn't try removing the cache. That may have solved the issue. |
feross
changed the title
standard --fix doesn't work on Windows
standard --fix doesn't work sometimes
Sep 22, 2016
This comment has been minimized.
This comment has been minimized.
kinyat
commented
Oct 6, 2016
|
I have an issue when migrating to standardJS, it wont auto align for the code written in JSX. |
This comment has been minimized.
This comment has been minimized.
This really nails it. Thanks for explaining the issue. Now we just need a reproducible case where this happens and we can report it to the ESLint project as a bug. |
This comment has been minimized.
This comment has been minimized.
|
@kinyat This issue is about something different than your issue. If you want, you can open a new issue and one of the contributors will look into it further. But note: Not all rules are automatically fixable, but more are added all the time. |
This comment has been minimized.
This comment has been minimized.
prashanth-kalaga
commented
Jan 6, 2017
|
|
This comment has been minimized.
This comment has been minimized.
|
@prashanth-kalaga Only certain statically-verifiable cases of the |
This comment has been minimized.
This comment has been minimized.
|
I'm closing this issue because it's been a while without any new information. It's not possible to debug this issue without additional information. If this is still an issue, please leave a comment or open a new issue. |
feross
closed this
Jan 7, 2017
This comment has been minimized.
This comment has been minimized.
ChrisMorrisOrg
commented
Feb 28, 2017
|
I've actually just run into this issue as well. Here is the output:
|
This comment has been minimized.
This comment has been minimized.
mrchief
commented
Feb 28, 2017
|
@ChrisMorrisOrg I doubt if anyone looks at closed issues. You should open a new one. |

dcposch commentedSep 19, 2016
Using Node.js command prompt: