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
Part of the benefit of Prettier it is that it runs automatically, allowing the dev to code with whatever style looks/feels right at the moment then on commit, code gets standardized. Prettier errors via eslint are not only unnecessary but are distracting during development as they get mixed in with actual eslint errors and warnings.
Example:
The text was updated successfully, but these errors were encountered:
ESLint also contains code formatting rules, which can conflict with your existing Prettier setup. We recommend including eslint-config-prettier in your ESLint config to make ESLint and Prettier work together.
Are you ok leaving eslint-config-prettier, but then removing eslint-plugin-prettier? I've submitted a PR #145 to test this approach out.
One regression I just realized, we had VSCode configured to disable prettier, and run eslint fix on save. We need to adjust that if we're going this route.
Part of the benefit of Prettier it is that it runs automatically, allowing the dev to code with whatever style looks/feels right at the moment then on commit, code gets standardized. Prettier errors via eslint are not only unnecessary but are distracting during development as they get mixed in with actual eslint errors and warnings.
Example:
The text was updated successfully, but these errors were encountered: