You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sounds reasonable to me. Is the assumption that users would create a .prettierrc file if they want to use a non-default prettier config? (Without a .prettierrc file, the user would have to override the prettier/prettier rule config in order to use something other than the prettier defaults, which would partially defeat the point of including it in a separate config.)
Another option would be to just export eslint-config-prettier as its own config, without enabling prettier/prettier.
Is the assumption that users would create a .prettierrc file if they want to use a non-default prettier config?
Yes. This is recommended because editor extensions such as prettier-atom and prettier-vscodewill read .prettierrc, but won't read settings from ESLint, which can lead to an inconsistent experience.
Usually when I set up a project with Prettier I use both
eslint-{plugin,config}-prettier
.What would be great is if this module exported a
"recommended"
configuration that did this for me:Effectively:
Would such an addition be welcome?
The text was updated successfully, but these errors were encountered: