Skip to content
Permalink
Browse files

Docs: Fix typo in 6.0.0 migration guide (#11870)

  • Loading branch information...
platinumazure committed Jun 22, 2019
1 parent a7985a6 commit f3a0774a8879b08777a4aedc76677f13d5156242
Showing with 1 addition and 1 deletion.
  1. +1 −1 docs/user-guide/migrating-to-6.0.0.md
@@ -61,7 +61,7 @@ Additionally, the following rule has been *removed* from `eslint:recommended`:

* [`no-console`](https://eslint.org/docs/rules/no-console) disallows calling functions like `console.log`. While this rule is useful in many cases (e.g. to avoid inadvertently leaving debugging statements in production code), it is not as broadly applicable as the other rules in `eslint:recommended`, and it was a source of false positives in cases where `console.log` is acceptable (e.g. in CLI applications).

Finally, in ESLint v5 `eslint:recommended` would explicitly disable all core rules that were not considered "recommended". This could cause confusion behavior if `eslint:recommended` was loaded after another config, since `eslint:recommended` would have the effect of turning off some rules. In ESLint v6, `eslint:recommended` has no effect on non-recommended rules.
Finally, in ESLint v5 `eslint:recommended` would explicitly disable all core rules that were not considered "recommended". This could cause confusing behavior if `eslint:recommended` was loaded after another config, since `eslint:recommended` would have the effect of turning off some rules. In ESLint v6, `eslint:recommended` has no effect on non-recommended rules.

**To address:** To mimic the `eslint:recommended` behavior from 5.x, you can explicitly disable/enable rules in a config file as follows:

0 comments on commit f3a0774

Please sign in to comment.
You can’t perform that action at this time.