Skip to content

fix(linter): allow options for eslint/capitalized-comments#23139

Merged
graphite-app[bot] merged 1 commit into
mainfrom
06-08-fix_linter_allow_options_for_eslint_capitalized-comments_
Jun 9, 2026
Merged

fix(linter): allow options for eslint/capitalized-comments#23139
graphite-app[bot] merged 1 commit into
mainfrom
06-08-fix_linter_allow_options_for_eslint_capitalized-comments_

Conversation

@Sysix

@Sysix Sysix commented Jun 8, 2026

Copy link
Copy Markdown
Member

fixes #23122

was introduced in #22984, where we removed the config = line.

Sysix commented Jun 8, 2026

Copy link
Copy Markdown
Member Author

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 changes, fast-track this PR to the front of the merge queue

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.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions github-actions Bot added A-linter Area - Linter A-cli Area - CLI labels Jun 8, 2026
@Sysix Sysix marked this pull request as ready for review June 8, 2026 19:49
@codspeed-hq

codspeed-hq Bot commented Jun 8, 2026

Copy link
Copy Markdown

Merging this PR will not alter performance

✅ 5 untouched benchmarks
⏩ 66 skipped benchmarks1


Comparing 06-08-fix_linter_allow_options_for_eslint_capitalized-comments_ (e6c5b80) with main (01b74c4)

Open in CodSpeed

Footnotes

  1. 66 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 camc314 added the 0-merge Merge with Graphite Merge Queue label Jun 9, 2026
@camc314 camc314 self-assigned this Jun 9, 2026

camc314 commented Jun 9, 2026

Copy link
Copy Markdown
Contributor

Merge activity

fixes #23122

was introduced in #22984, where we removed the `config = ` line.
@graphite-app graphite-app Bot force-pushed the 06-08-fix_linter_allow_options_for_eslint_capitalized-comments_ branch from e6c5b80 to 8f3db61 Compare June 9, 2026 08:20
@graphite-app graphite-app Bot merged commit 8f3db61 into main Jun 9, 2026
29 checks passed
@graphite-app graphite-app Bot removed the 0-merge Merge with Graphite Merge Queue label Jun 9, 2026
@graphite-app graphite-app Bot deleted the 06-08-fix_linter_allow_options_for_eslint_capitalized-comments_ branch June 9, 2026 08:25
graphite-app Bot pushed a commit that referenced this pull request Jun 9, 2026
follow up from #23139

Added tests when a test-case has an option but the `rule.has_config()`, making sure this code path will never hit for rules which should have a config:
https://github.com/oxc-project/oxc/blob/01b74c4e84696950add4b813b0dfa2600c459f09/crates/oxc_linter/src/config/rules.rs#L158-L165

On the way I found some rules where the test-cases shown us options for rules, which we do not support atm.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-cli Area - CLI A-linter Area - Linter

Projects

None yet

Development

Successfully merging this pull request may close these issues.

linter: eslint/capitalized-comments fails with options configuration

2 participants