From 532ae8b1114589eb5e3750c6f011de026b28ef29 Mon Sep 17 00:00:00 2001 From: Xinyu Liu Date: Mon, 25 Mar 2024 23:29:26 +0800 Subject: [PATCH] docs: fix typo in switch-exhaustiveness-check (#8768) --- .../eslint-plugin/docs/rules/switch-exhaustiveness-check.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/eslint-plugin/docs/rules/switch-exhaustiveness-check.mdx b/packages/eslint-plugin/docs/rules/switch-exhaustiveness-check.mdx index a4de1ae6877..f629d8ee53a 100644 --- a/packages/eslint-plugin/docs/rules/switch-exhaustiveness-check.mdx +++ b/packages/eslint-plugin/docs/rules/switch-exhaustiveness-check.mdx @@ -34,7 +34,7 @@ If your project has many intentionally redundant `default` cases, you may want t ### `requireDefaultForNonUnion` -Defaults to false. It set to true, this rule will also report when a `switch` statement switches over a non-union type (like a `number` or `string`, for example) and that `switch` statement does not have a `default` case. Thus, by setting this option to true, the rule becomes stricter. +Defaults to false. If set to true, this rule will also report when a `switch` statement switches over a non-union type (like a `number` or `string`, for example) and that `switch` statement does not have a `default` case. Thus, by setting this option to true, the rule becomes stricter. This is generally desirable so that `number` and `string` switches will be subject to the same exhaustive checks that your other switches are.