docs(linter): describe problems on not verified rules schema (#23351)

This commit is contained in:
Sysix committed 2026-06-12 14:26:50 +00:00
1 parent 231d5dec4d
commit 2120ecfb45
1 file changed
+10 -10
+10 -10
View File
@@ -14,14 +14,17 @@ use crate::rules::RuleEnum;
/// until we verify that the rule's schema is valid and can be generated by schemars.
#[cfg(feature = "ruledocs")]
const NO_VERIFIED_VALID_SCHEMA: [&str; 35] = [
"eslint/func-name-matching",
"eslint/no-restricted-globals",
"eslint/no-restricted-imports",
"eslint/no-restricted-properties",
"eslint/func-name-matching", // second config can be on first position like [AllowWarnDeny, Config1, Config2] | [AllowWarnDeny, Config1] | [AllowWarnDeny, Config2]
"eslint/no-restricted-globals", // uses spread syntax like [AllowWarnDeny, ...Config]
"eslint/no-restricted-imports", // uses spread syntax like [AllowWarnDeny, ...Config]
"eslint/no-restricted-properties", // uses spread syntax like [AllowWarnDeny, ...Config]
"node/callback-return", // uses array syntax [AllowWarnDeny, string[]]
"eslint/prefer-destructuring",
"import/extensions",
"jest/prefer-lowercase-title",
"jest/valid-title",
"import/extensions", // second config can be on first position like[AllowWarnDeny, Config1, Config2] | [AllowWarnDeny, Config1] | [AllowWarnDeny, Config2]
"jest/prefer-lowercase-title", // has options from other rule
"jest/valid-title", // has options from other rule
"vitest/prefer-lowercase-title", // has options from other rule
"vitest/valid-title", // has options from other rule
"jsdoc/require-param",
"jsx_a11y/alt-text",
"jsx_a11y/anchor-is-valid",
@@ -32,7 +35,6 @@ const NO_VERIFIED_VALID_SCHEMA: [&str; 35] = [
"jsx_a11y/no-distracting-elements",
"jsx_a11y/no-noninteractive-element-to-interactive-role",
"jsx_a11y/no-interactive-element-to-noninteractive-role",
"node/callback-return",
"react/exhaustive-deps",
"react/jsx-curly-brace-presence",
"react/jsx-handler-names",
@@ -47,8 +49,6 @@ const NO_VERIFIED_VALID_SCHEMA: [&str; 35] = [
"unicorn/import-style",
"unicorn/numeric-separators-style",
"unicorn/prefer-at",
"vitest/prefer-lowercase-title",
"vitest/valid-title",
];
/// Should this rule be skipped for config schema generation?