-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lint by default #106
Comments
I think it makes sense, still some people seem surprised that it can lint things |
On the other hand prettier-standard is used for auto-formatting (e.g. when saving files) without linting. I think it would break many setups if I enabled linting by default because it would cause formatting to fail even if single linting error is present. Maybe just a message at the end that you can use |
+1, yes |
Hey @sheerun, thanks for the formatter! On the topic of linting, I noticed that we are not able to fix fixable rules picked up by the --lint flag by using |
prettier-standard doesn't fix linting errors by default (only formatting ones). I guess I could introduce |
Supporting the combo |
+1 |
Hi, Sorry for asking this unrelated question but I'm stuck on this for a while and can't find a way for this. Can you please guide me how can I enable prettier-standard for auto-formatting when saving files in VS Code. Any help would be highly appreciated |
I discovered pretty recently that the
--lint
option is needed to enable some of the lint rules fromstandard
.I would favor that this option is enabled by default, considering that this utility seems to be intended to apply a combination of both Prettier formatting and
standard
code lint functionality.I would also love to see an option to both fix the formatting and fix as many eslint issues as possible at the same time.
Thanks again for making and maintaining this utility!
The text was updated successfully, but these errors were encountered: