docs(linter): Add config option docs for various rules.

[connorshea]

Part of #14743.

• typescript/consistent-type-imports
• eslint/no-else-return
• react/state-in-constructor
• eslint/no-cond-assign
• eslint/default-case
• react/jsx-handler-names
• eslint/new-cap

Generated docs:

typescript/consistent-type-imports:

## Configuration

This rule accepts a configuration object with the following properties:

### disallowTypeAnnotations

type: `boolean`

Disallow using `import()` in type annotations, like `type T = import('foo')`


### fixStyle

type: `"separate-type-imports" | "inline-type-imports"`

Control how type imports are added when auto-fixing.


#### `"separate-type-imports"`

Will add the type keyword after the import keyword `import type { A } from '...'`


#### `"inline-type-imports"`

Will inline the type keyword `import { type A } from '...'` (only available in TypeScript 4.5+)


### prefer

type: `"type-imports" | "no-type-imports"`


Control whether to enforce type imports or value imports.


#### `"type-imports"`

Will enforce that you always use `import type Foo from '...'` except referenced by metadata of decorators.


#### `"no-type-imports"`

Will enforce that you always use `import Foo from '...'`

eslint/no-else-return:

## Configuration

This rule accepts a configuration object with the following properties:

### allowElseIf

type: `boolean`

default: `true`

Whether to allow `else if` blocks after a return statement.

Examples of **incorrect** code for this rule with `allowElseIf: false`:
\```javascript
function foo() {
if (error) {
return 'It failed';
} else if (loading) {
return "It's still loading";
}
}
\```

Examples of **correct** code for this rule with `allowElseIf: false`:
\```javascript
function foo() {
if (error) {
return 'It failed';
}

if (loading) {
return "It's still loading";
}
}
\```

react/state-in-constructor:

## Configuration

This rule accepts one of the following string values:

### `"always"`

Enforce state initialization in the constructor.

### `"never"`

Enforce state initialization with a class property.

eslint/no-cond-assign:

## Configuration

This rule accepts one of the following string values:

### `"except-parens"`

Allow assignments in conditional expressions only if they are
enclosed in parentheses.


### `"always"`

Disallow all assignments in conditional expressions.

eslint/default-case:

## Configuration

This rule accepts a configuration object with the following properties:

### commentPattern

type: `[
  string,
  null
]`

A regex pattern used to detect comments that mark the absence
of a `default` case as intentional.

Default value: `no default`.

Examples of **incorrect** code for this rule with the `{ "commentPattern": "^skip\\sdefault" }` option:
\```js
/* default-case: ["error", { "commentPattern": "^skip\sdefault" }] */

switch (a) {
case 1:
break;
// no default
}
\```

Examples of **correct** code for this rule with the `{ "commentPattern": "^skip\\sdefault" }` option:
\```js
/* default-case: ["error", { "commentPattern": "^skip\\sdefault" }] */

switch (a) {
case 1:
break;
// skip default
}
\```

eslint/no-fallthrough:

## Configuration

This rule accepts a configuration object with the following properties:

### allowEmptyCase

type: `boolean`

default: `false`

Whether to allow empty case clauses to fall through.


### commentPattern

type: `[
  string,
  null
]`


Custom regex pattern to match fallthrough comments.


### reportUnusedFallthroughComment

type: `boolean`

default: `false`

Whether to report unused fallthrough comments.

react/jsx-handler-names:

## Configuration

This rule accepts a configuration object with the following properties:

### checkInlineFunctions

type: `boolean`

default: `false`

Whether to check for inline functions in JSX attributes.

### checkLocalVariables

type: `boolean`

default: `false`

Whether to check for local variables in JSX attributes.

### eventHandlerPrefixes

type: `string`

default: `"handle"`

Event handler prefixes to check against.

### eventHandlerPropPrefixes

type: `string`

default: `"on"`

Event handler prop prefixes to check against.

### eventHandlerPropRegex

type: `[
  string,
  null
]`

Compiled regex for event handler prop prefixes.


### eventHandlerRegex

type: `[
  string,
  null
]`

Compiled regex for event handler prefixes.

### ignoreComponentNames

type: `string[]`

default: `[]`

Component names to ignore when checking for event handler prefixes.

eslint/new-cap:

## Configuration

This rule accepts a configuration object with the following properties:

### capIsNew

type: `boolean`

default: `true`

Whether to enforce that functions with names starting with an uppercase letter are only used as constructors.


### capIsNewExceptionPattern

type: `[
  string,
  null
]`


A regex pattern to match exceptions for functions with names starting with an uppercase letter.


### capIsNewExceptions

type: `string[]`

default: `[]`

Exceptions to ignore for functions with names starting with an uppercase letter.


### newIsCap

type: `boolean`

default: `true`

Whether to enforce that constructor names start with an uppercase letter.


### newIsCapExceptionPattern

type: `[
  string,
  null
]`


A regex pattern to match exceptions for constructor names starting with an uppercase letter.


### newIsCapExceptions

type: `string[]`

default: `["Array", "Boolean", "Date", "Error", "Function", "Number", "Object", "RegExp", "String", "Symbol", "BigInt"]`

Exceptions to ignore for constructor names starting with an uppercase letter.


### properties

type: `boolean`

default: `true`

Whether to check member expressions (e.g., `obj.Method()`).

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[Copilot]

Pull request overview

This PR adds configuration option documentation for 7 linter rules, making them accessible through auto-generated schemas. The changes enable users to understand available configuration options directly from the generated documentation.

• Adds JsonSchema derives and doc comments to configuration structs for better documentation generation
• Updates error messages to use backticks instead of single quotes for code elements (e.g., `break` instead of 'break')
• Removes rules from the test exception list now that they have proper configuration documentation

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
rule_configuration_documentation_test.rs	Removes 7 rules from the exceptions list that now have configuration documentation
eslint_no_fallthrough.snap	Updates snapshot to reflect backtick usage in error messages
eslint_no_else_return.snap	Updates snapshot to reflect backtick usage in error messages
eslint_default_case.snap	Updates snapshot to reflect backtick usage in error messages
consistent_type_imports.rs	Adds JsonSchema support, field-level documentation, and registers config with macro
state_in_constructor.rs	Adds JsonSchema support, enum variant documentation, and registers config with macro
jsx_handler_names.rs	Adds JsonSchema support, field-level documentation, and registers config with macro
no_fallthrough.rs	Adds JsonSchema support, refactors config struct, updates error messages to use backticks
no_else_return.rs	Adds JsonSchema support, moves diagnostic function, adds comprehensive field documentation with examples
no_cond_assign.rs	Adds JsonSchema support, adds enum variant documentation, and registers config with macro
default_case.rs	Adds JsonSchema support, adds comprehensive field documentation with examples, updates error messages to use backticks

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codspeed-hq]

CodSpeed Performance Report

Merging #16024 will not alter performance

_{Comparing more-docs (066489a) with main (3976e4f)}

Summary

✅ 4 untouched
⏩ 41 skipped¹

Footnotes

1. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[camc314]

Merge activity

• Nov 24, 9:12 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Nov 24, 9:12 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Nov 24, 9:19 AM UTC: Merged by the Graphite merge queue.