From 06969e91c68731ff1aea522d46bb7a4968c48315 Mon Sep 17 00:00:00 2001 From: chenxsan Date: Tue, 29 Jun 2021 21:23:44 +0800 Subject: [PATCH 1/2] Docs: remove superfluous whitespace --- docs/rules/no-inner-declarations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rules/no-inner-declarations.md b/docs/rules/no-inner-declarations.md index 707fc6e781f..9bdfaa7c400 100644 --- a/docs/rules/no-inner-declarations.md +++ b/docs/rules/no-inner-declarations.md @@ -1,4 +1,4 @@ -# disallow variable or `function` declarations in nested blocks (no-inner-declarations) +# disallow variable or `function` declarations in nested blocks (no-inner-declarations) In JavaScript, prior to ES6, a function declaration is only allowed in the first level of a program or the body of another function, though parsers sometimes [erroneously accept them elsewhere](https://code.google.com/p/esprima/issues/detail?id=422). This only applies to function declarations; named or anonymous function expressions can occur anywhere an expression is permitted. From b32f8d07b924c78471de301ef9cccc6fae981820 Mon Sep 17 00:00:00 2001 From: chenxsan Date: Tue, 29 Jun 2021 21:27:50 +0800 Subject: [PATCH 2/2] Docs: update links --- docs/developer-guide/working-with-rules.md | 2 +- docs/user-guide/configuring/configuration-files.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/developer-guide/working-with-rules.md b/docs/developer-guide/working-with-rules.md index a269e1c5fa4..c15f77c4cd1 100644 --- a/docs/developer-guide/working-with-rules.md +++ b/docs/developer-guide/working-with-rules.md @@ -66,7 +66,7 @@ The source file for a rule exports an object with the following properties. In a custom rule or plugin, you can omit `docs` or include any properties that you need in it. -* `fixable` (string) is either `"code"` or `"whitespace"` if the `--fix` option on the [command line](../user-guide/command-line-interface.md#-fix) automatically fixes problems reported by the rule +* `fixable` (string) is either `"code"` or `"whitespace"` if the `--fix` option on the [command line](../user-guide/command-line-interface.md#--fix) automatically fixes problems reported by the rule **Important:** the `fixable` property is mandatory for fixable rules. If this property isn't specified, ESLint will throw an error whenever the rule attempts to produce a fix. Omit the `fixable` property if the rule is not fixable. diff --git a/docs/user-guide/configuring/configuration-files.md b/docs/user-guide/configuring/configuration-files.md index e8aa6bf0e77..bf9b70d12db 100644 --- a/docs/user-guide/configuring/configuration-files.md +++ b/docs/user-guide/configuring/configuration-files.md @@ -37,7 +37,7 @@ The second way to use configuration files is to save the file wherever you would eslint -c myconfig.json myfiletotest.js -If you are using one configuration file and want ESLint to ignore any `.eslintrc.*` files, make sure to use [`--no-eslintrc`](https://eslint.org/docs/user-guide/command-line-interface#-no-eslintrc) along with the [`-c`](https://eslint.org/docs/user-guide/command-line-interface#-c-config) flag. +If you are using one configuration file and want ESLint to ignore any `.eslintrc.*` files, make sure to use [`--no-eslintrc`](https://eslint.org/docs/user-guide/command-line-interface#--no-eslintrc) along with the [`-c`](https://eslint.org/docs/user-guide/command-line-interface#-c---config) flag. ### Comments in configuration files