ch3rry aa49d86046 fix(linter): allow spread rule options in config types (#25675) ...

## Summary

- represent variadic rule options as a severity followed by zero or more
option values
- regenerate the Oxlint configuration schema and TypeScript declarations
- add a type-level regression for mapped options spread into
`no-restricted-globals`

## Root cause

The schema wrapper materialized the first `additionalItems` entry as a
required tuple element and set `minItems` to 2. A dynamic TypeScript
spread has type `T[]` and may be empty, so it cannot satisfy that
required position even though the severity-only form is already valid
through `RuleNoConfig`.

Keeping severity as the only fixed tuple item and leaving the rule
options in `additionalItems` generates `[severity, ...options]`, which
accepts both an empty spread and populated spreads without changing
runtime rule behavior.

Closes #25666


## AI assistance

Implemented with assistance from OpenAI Codex. The contributor remains
responsible for reviewing, understanding, and submitting the change
under the repository AI usage policy.

---------

Co-authored-by: Cameron <cameron.clark@hey.com>

2026-08-17 14:11:07 +01:00

..

oxfmt

docs(oxfmt/conformance): Update notes on conformance (#25757)

2026-08-17 09:25:11 +09:00

oxlint

fix(linter): allow spread rule options in config types (#25675)

2026-08-17 14:11:07 +01:00

shared

refactor(oxlint,oxfmt): Fix up apps/shared usage (#22457)

2026-05-20 08:21:39 +00:00