It doesn’t matter which approach you use.
Put "prettier/prettier" in your "extends".That’s eslint- plugin-prettier’s recommended config. Put "plugin:prettier/recommended" in your "extends".There are a couple of ways to turn these rules off: See the arrow-body-style and prefer-arrow-callback issue for details. These rules might cause problems if using eslint-plugin-prettier and -fix.
arrow-body-style and prefer-arrow-callback If you want them, you need to explicitly specify them in your ESLint config. Some can cause problems if using eslint-plugin-prettier and -fix.įor maximum ease of use, the special rules are disabled by default (provided that you include all needed things in "extends").The CLI helper tool warns you if any of those rules are enabled, but can’t tell if anything is problematic. Some require special attention when writing code.There a few rules that eslint-config-prettier disables that actually can be enabled in some cases. But if you use multiple configuration files or overrides, you can provide several files to check: Usually you’ll have about the same rules for all files, so it is good enough to run the command on one file. In theory you need to run the tool for every single file in your project to be 100% sure that there are no conflicting rules, because ESLint supports having different rules for different files. Instead you might want to actually have your own rules after eslint-config-prettier and run the CLI helper tool to find out about problems, so you can remove conflicting rules from the config file altogether (simplifying your config). It looks like we enable the indent rule, but in reality it’s disabled thanks to the eslintConfigPrettier line below it. However, looking at the above config might feel confusing. Import typescriptEslint from import eslintConfigPrettier from "eslint-config-prettier" export default
0 kommentar(er)
