-
Notifications
You must be signed in to change notification settings - Fork 107
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
Get rid of "format-all-ensure-formatter" #133
Comments
The point of not using a formatter automatically is that many projects do not use code formatters (or they use a formatter for some languages, but not for others). If you have a default formatter, and use it to format code belonging to those projects, the formatting will likely be incorrect according to the style guide of that project. I agree that it's confusing that you have to remember to call |
Also, setting |
Thanks for your fast response! You are right, the semantics make sense and are pretty logical. But maybe you should add your explanation to the README as it currently isn't very clear on that point. 😄 Also, I find that adding a hook to a package in order to run that package slightly counter-intuitive. My idea is to remove the Just my two cents. In case you want to brain-storm, go ahead. 😄 |
Hi!
Is there really a good use case for
format-all-ensure-formatter
? To me, it seems like like a superfluous option that only does what a normal user would expect anyway. But maybe I'm just being blind here.Still, I think that you should
format-all-ensure-formatter
(and call it behind the scenes), orformat-all-do-not-ensure-formatter
Thanks for your package – now that I call
format-all-ensure-formatter
from a hook it works great! It seems that I skipped that paragraph when reading the manual... 😄Martin
The text was updated successfully, but these errors were encountered: