-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
docs: improve why usePrettierrc
option is needed
#506
Comments
#83 was before my time. It is possible to run prettier without loading the prettierrc config file via the CLI's --no-config option or through the API by calling I suspect #83 was added to maintain parity with those options, because somebody was creating some tool that wrapped over prettier/eslint with a set of hardcoded, unconfigurable settings. I agree that 99% of the time users should won't need this functionality, and that they should rely on settings their options in their .prettierrc file. However somebody clearly had a need for it and the maintenance overhead is negligible, so I think it is worthwhile to keep this setting. |
I want to understand in which case a user would want a different config between ESLint and prettier itself.
This seems reasonable, so closing. But the document could be improved, so that any further maintainer won't be confused like me. |
usePrettierrc
optionusePrettierrc
option is needed
close via #510 |
@BPScott I don't quite understand why we add
usePrettierrc
option in #83,prettierrc
is used for all tools, it should always be preferred, I have no idea about in which case we should have inconsistent prettier settings, what do you think?Maybe @eliperelman @azz @not-an-aardvark can help me to understand?
Originally posted by @JounQin in #481 (comment)
The text was updated successfully, but these errors were encountered: