From c444b01830c932695d12780fd03a6d509be1c848 Mon Sep 17 00:00:00 2001 From: Rel1cx Date: Fri, 17 Oct 2025 03:56:26 +0800 Subject: [PATCH 1/2] Simplify "Which one should I use? Unified plugin or individual plugins?" in faq --- apps/website/content/docs/faq.mdx | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/apps/website/content/docs/faq.mdx b/apps/website/content/docs/faq.mdx index 1d95f8e22..91dc78e83 100644 --- a/apps/website/content/docs/faq.mdx +++ b/apps/website/content/docs/faq.mdx @@ -55,13 +55,7 @@ import { Accordion, Accordions } from "fumadocs-ui/components/accordion"; For users who use the presets we provide (such as `recommended` or `strict`), it is recommended to use the unified plugin `@eslint-react/eslint-plugin`. This simplifies configuration and ensures that all relevant rules are enabled correctly. - For users who need more fine-grained control, choose to use the unified plugin or individual plugins depending on the degree of modification relative to the initial presets we provide: - - - **Minor Adjustments**: If you only need to make minor adjustments to the presets (for example, disabling some rules or adding a few custom rules), it is recommended to continue using the unified plugin `@eslint-react/eslint-plugin`. This makes managing the configuration simpler while still benefiting from the comprehensiveness of the presets. - - **Major Customization**: If you need to make significant changes to the rule set (for example, using only the rules of a specific plugin, or requiring a completely different rule set), it is recommended to use individual plugins (such as `eslint-plugin-react-x`, `eslint-plugin-react-dom`, etc.). This - allows you to have full control over the enabled rules and customize them according to your project's needs. - - For users who want to build and maintain an ESLint configuration for themselves or their organization, it is **always recommended to use individual plugins**. This allows you to freely select plugins and compose rules as needed, without being limited by presets. + For users who need more fine-grained control or build and maintain an ESLint configuration for themselves or their organization, it is recommended to use individual plugins. This allows you to freely select plugins and compose rules as needed, without being limited by presets The unified plugin (`@eslint-react/eslint-plugin`) contains some historical decisions and internal behaviors that were originally made to be compatible with both Legacy Config and Flat Config. Reducing external package dependencies on it is better in the long run. From 74350a0d10845833de47c1c1bf4fd721f74540db Mon Sep 17 00:00:00 2001 From: REL1CX Date: Fri, 17 Oct 2025 03:59:56 +0800 Subject: [PATCH 2/2] Update apps/website/content/docs/faq.mdx Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: REL1CX --- apps/website/content/docs/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/website/content/docs/faq.mdx b/apps/website/content/docs/faq.mdx index 91dc78e83..b8c11a307 100644 --- a/apps/website/content/docs/faq.mdx +++ b/apps/website/content/docs/faq.mdx @@ -55,7 +55,7 @@ import { Accordion, Accordions } from "fumadocs-ui/components/accordion"; For users who use the presets we provide (such as `recommended` or `strict`), it is recommended to use the unified plugin `@eslint-react/eslint-plugin`. This simplifies configuration and ensures that all relevant rules are enabled correctly. - For users who need more fine-grained control or build and maintain an ESLint configuration for themselves or their organization, it is recommended to use individual plugins. This allows you to freely select plugins and compose rules as needed, without being limited by presets + For users who need more fine-grained control or build and maintain an ESLint configuration for themselves or their organization, it is recommended to use individual plugins. This allows you to freely select plugins and compose rules as needed, without being limited by presets. The unified plugin (`@eslint-react/eslint-plugin`) contains some historical decisions and internal behaviors that were originally made to be compatible with both Legacy Config and Flat Config. Reducing external package dependencies on it is better in the long run.