docs: Regenerate docs with latest fixes. (#680)

* docs: Regenerate docs with latest fixes.

None of these are functionality changes or represent changes to the oxlint/oxfmt codebases themselves as far as I'm aware. This just fixes the header depths and adds/fixes some docs for rules that lacked them or were incorrect.

* Fix the generated-config.md depth

Author: connorshea

src/docs/guide/usage/formatter/generated-config.md

@@ -7,7 +7,7 @@ search: false
 Most options are the same as Prettier's options.
 See also <https://prettier.io/docs/options>
 
-# arrowParens
+## arrowParens
 
 type: `string | null`
 
@@ -25,65 +25,69 @@ type: `boolean | null`
 
 Print spaces between brackets in object literals. (Default: true)
 
-# embeddedLanguageFormatting
+## embeddedLanguageFormatting
 
 type: `string | null`
 
 Control whether formats quoted code embedded in the file. (Default: "auto")
 
-# endOfLine
+## endOfLine
 
 type: `string | null`
 
 Which end of line characters to apply. (Default: "lf")
 
-# experimentalSortImports
+## experimentalSortImports
 
 type: `object | null`
 
 Experimental: Sort import statements. Disabled by default.
 
-## experimentalSortImports.groups
+### experimentalSortImports.groups
 
 type: `array | null`
 
 Custom groups configuration for organizing imports.
 Each array element represents a group, and multiple group names in the same array are treated as one.
 Accepts both `string` and `string[]` as group elements.
 
-### experimentalSortImports.groups[n]
+#### experimentalSortImports.groups[n]
 
 type: `string[]`
 
-## experimentalSortImports.ignoreCase
+### experimentalSortImports.ignoreCase
 
 type: `boolean`
 
 default: `true`
 
-## experimentalSortImports.newlinesBetween
+### experimentalSortImports.internalPattern
+
+type: `string[]`
+
+### experimentalSortImports.newlinesBetween
 
 type: `boolean`
 
 default: `true`
 
-# experimentalSortImports.order
+### experimentalSortImports.order
 
 type: `string | null`
 
-## experimentalSortImports.partitionByComment
+### experimentalSortImports.partitionByComment
 
 type: `boolean`
 
 default: `false`
 
-## experimentalSortImports.partitionByNewline
+### experimentalSortImports.partitionByNewline
 
 type: `boolean`
 
 default: `false`
 
-## experimentalSortImports.sortSideEffects
+### experimentalSortImports.sortSideEffects
 
 type: `boolean`
 
@@ -101,7 +105,7 @@ type: `boolean | null`
 
 Use single quotes instead of double quotes in JSX. (Default: false)
 
-# objectWrap
+## objectWrap
 
 type: `string | null`
 
@@ -114,7 +118,7 @@ type: `integer | null`
 
 The line length that the printer will wrap on. (Default: 100)
 
-# quoteProps
+## quoteProps
 
 type: `string | null`
 
@@ -144,7 +148,7 @@ type: `integer | null`
 
 Number of spaces per indentation level. (Default: 2)
 
-# trailingComma
+## trailingComma
 
 type: `string | null`
 

src/docs/guide/usage/linter/generated-config.md

@@ -165,7 +165,7 @@ type: `array`
 
 type: `object`
 
-### overrides[n].env
+#### overrides[n].env
 
 type: `object | null`
 
@@ -177,7 +177,7 @@ type: `string[]`
 
 A set of glob patterns.
 
-### overrides[n].globals
+#### overrides[n].globals
 
 type: `object | null`
 
@@ -192,7 +192,7 @@ JS plugins for this override.
 Note: JS plugins are experimental and not subject to semver.
 They are not supported in language server at present.
 
-### overrides[n].plugins
+#### overrides[n].plugins
 
 type: `array | null`
 
@@ -201,13 +201,17 @@ default: `null`
 Optionally change what plugins are enabled for this override. When
 omitted, the base config's plugins are used.
 
+##### overrides[n].plugins[n]
+
+type: `string`
+
 #### overrides[n].rules
 
 type: `object`
 
 See [Oxlint Rules](https://oxc.rs/docs/guide/usage/linter/rules.html)
 
-# plugins
+## plugins
 
 type: `array | null`
 
@@ -220,6 +224,10 @@ You can view the list of available plugins on
 NOTE: Setting the `plugins` field will overwrite the base set of plugins.
 The `plugins` array should reflect all of the plugins you want to use.
 
+### plugins[n]
+
+type: `string`
+
 ## rules
 
 type: `object`
@@ -383,10 +391,7 @@ Example:
 
 #### settings.jsx-a11y.polymorphicPropName
 
-type: `[
-  string,
-  null
-]`
+type: `string | null`
 
 An optional setting that define the prop your code uses to create polymorphic components.
 This setting will be used to determine the element type in rules that
@@ -409,7 +414,11 @@ Configure Next.js plugin rules.
 
 #### settings.next.rootDir
 
-type: `string | array`
+type: `array | string`
+
+##### settings.next.rootDir[n]
+
+type: `string`
 
 ### settings.react
 
@@ -447,7 +456,15 @@ Example:
 
 ##### settings.react.formComponents[n]
 
-type: `string | object | object`
+type: `object | string`
+
+###### settings.react.formComponents[n].attribute
+
+type: `string`
+
+###### settings.react.formComponents[n].name
+
+type: `string`
 
 #### settings.react.linkComponents
 
@@ -478,7 +495,15 @@ Example:
 
 ##### settings.react.linkComponents[n]
 
-type: `string | object | object`
+type: `object | string`
+
+###### settings.react.linkComponents[n].attribute
+
+type: `string`
+
+###### settings.react.linkComponents[n].name
+
+type: `string`
 
 ### settings.vitest
 

src/docs/guide/usage/linter/rules/eslint/default-case.md

@@ -68,10 +68,7 @@ This rule accepts a configuration object with the following properties:
 
 ### commentPattern
 
-type: `[
-  string,
-  null
-]`
+type: `string | null`
 
 A regex pattern used to detect comments that mark the absence
 of a `default` case as intentional.

src/docs/guide/usage/linter/rules/eslint/func-style.md

@@ -164,7 +164,7 @@ default: `false`
 
 When true, functions with type annotations are allowed regardless of the style setting.
 
-## namedExports
+### namedExports
 
 type: `string | null`
 

src/docs/guide/usage/linter/rules/eslint/new-cap.md

@@ -339,10 +339,7 @@ default: `true`
 
 ### capIsNewExceptionPattern
 
-type: `[
-  string,
-  null
-]`
+type: `string | null`
 
 A regex pattern to match exceptions for functions with names starting with an uppercase letter.
 
@@ -364,10 +361,7 @@ default: `true`
 
 ### newIsCapExceptionPattern
 
-type: `[
-  string,
-  null
-]`
+type: `string | null`
 
 A regex pattern to match exceptions for constructor names starting with an uppercase letter.
 

src/docs/guide/usage/linter/rules/eslint/no-extra-boolean-cast.md

@@ -36,7 +36,7 @@ var foo = Boolean(!!bar);
 if (!!foo) {}
 if (Boolean(foo)) {}
 
-// with "enforceForLogicalOperands" option enabled
+// with "enforceForInnerExpressions" option enabled
 if (!!foo || bar) {}
 ```
 
@@ -49,7 +49,7 @@ var foo = Boolean(bar);
 if (foo) {}
 if (foo) {}
 
-// with "enforceForLogicalOperands" option enabled
+// with "enforceForInnerExpressions" option enabled
 if (foo || bar) {}
 ```
 

src/docs/guide/usage/linter/rules/eslint/no-fallthrough.md

@@ -198,10 +198,7 @@ Whether to allow empty case clauses to fall through.
 
 ### commentPattern
 
-type: `[
-  string,
-  null
-]`
+type: `string | null`
 
 Custom regex pattern to match fallthrough comments.
 

src/docs/guide/usage/linter/rules/import/extensions.md

@@ -109,7 +109,7 @@ default: `"never"`
 
 Configuration for `.jsx` file extensions.
 
-## requireExtension
+### requireExtension
 
 type: `string | null`
 

src/docs/guide/usage/linter/rules/jest/consistent-test-it.md

@@ -57,43 +57,37 @@ describe("foo", function() {
 });
 ```
 
-#### Options
-
-This rule can be configured as follows
+This rule is compatible with [eslint-plugin-vitest](https://github.com/veritem/eslint-plugin-vitest/blob/v1.1.9/docs/rules/consistent-test-it.md),
+to use it, add the following configuration to your `.eslintrc.json`:
 
-```json5
+```json
 {
-    type: 'object',
-    properties: {
-        fn: {
-            enum: ['it', 'test'],
-        },
-        withinDescribe: {
-            enum: ['it', 'test'],
-        },
-    },
-    additionalProperties: false,
+  "rules": {
+    "vitest/consistent-test-it": "error"
+  }
 }
 ```
 
-##### fn
+## Configuration
+
+This rule accepts a configuration object with the following properties:
+
+### fn
+
+type: `"it" | "test"`
+
+default: `"test"`
 
 Decides whether to use `test` or `it`.
 
-##### withinDescribe
+### withinDescribe
 
-Decides whether to use `test` or `it` within a `describe` scope.
+type: `"it" | "test"`
 
-This rule is compatible with [eslint-plugin-vitest](https://github.com/veritem/eslint-plugin-vitest/blob/v1.1.9/docs/rules/consistent-test-it.md),
-to use it, add the following configuration to your `.eslintrc.json`:
+default: `"it"`
 
-```json
-{
-  "rules": {
-    "vitest/consistent-test-it": "error"
-  }
-}
-```
+Decides whether to use `test` or `it` within a `describe` scope.
+If only `fn` is provided, this will default to the value of `fn`.
 
 ## How to use