feat(linter): no-misleading-character-class add suggestions for regex literal#22681
Merged
graphite-app[bot] merged 1 commit intoMay 24, 2026
Conversation
Member
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via 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. |
Merging this PR will not alter performance
Comparing 
Footnotes
|
Sysix
force-pushed
the
05-22-feate_linter_no-misleading-character-class_add_suggestions_for_regex_literal
branch
from
411fb34 to
8b87e41
Compare
Sysix
force-pushed
the
05-22-fix_linter_respect_flags_overrides_for_regexp__regex_i_u_
branch
from
314bcb9 to
8a766d6
Compare
Sysix
changed the title
no-misleading-character-class add suggestions for regex literalno-misleading-character-class add suggestions for regex literal
Sysix
force-pushed
the
05-22-feate_linter_no-misleading-character-class_add_suggestions_for_regex_literal
branch
from
8b87e41 to
2760270
Compare
Sysix
force-pushed
the
05-22-fix_linter_respect_flags_overrides_for_regexp__regex_i_u_
branch
from
8a766d6 to
0e91242
Compare
Sysix
force-pushed
the
05-22-feate_linter_no-misleading-character-class_add_suggestions_for_regex_literal
branch
from
2760270 to
cca3ecb
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Adds fixer suggestions for no-misleading-character-class when the offending pattern comes from a RegExp literal (either standalone /.../ or passed as the first argument to RegExp(...) / new RegExp(...)). This aligns the rule’s autofix behavior across literal and constructor forms by validating patterns with the correct parser for each input kind.
Changes:
- Implement a
u-flag suggestion forAstKind::RegExpLiteralby appendinguto the literal when the pattern is valid under Unicode mode. - Extend constructor/call fixes to correctly validate and fix cases where the first argument is a RegExp literal (using
LiteralParserrather thanConstructorParser). - Update the rule’s fixer tests to include previously skipped RegExp-literal fix expectations.
camc314
approved these changes
May 24, 2026
Contributor
Merge activity
|
…ex literal (#22681) Adds fixer suggestions for `no-misleading-character-class` when the offending pattern comes from a RegExp *literal* (either standalone `/.../` or passed as the first argument to `RegExp(...)` / `new RegExp(...)`). This aligns the rule’s autofix behavior across literal and constructor forms by validating patterns with the correct parser for each input kind. **Changes:** - Implement a `u`-flag suggestion for `AstKind::RegExpLiteral` by appending `u` to the literal when the pattern is valid under Unicode mode. - Extend constructor/call fixes to correctly validate and fix cases where the first argument is a RegExp literal (using `LiteralParser` rather than `ConstructorParser`). - Update the rule’s fixer tests to include previously skipped RegExp-literal fix expectations.
graphite-app
Bot
force-pushed
the
05-22-fix_linter_respect_flags_overrides_for_regexp__regex_i_u_
branch
from
0e91242 to
ed445ba
Compare
graphite-app
Bot
force-pushed
the
05-22-feate_linter_no-misleading-character-class_add_suggestions_for_regex_literal
branch
from
cca3ecb to
10da26b
Compare
Base automatically changed from
05-22-fix_linter_respect_flags_overrides_for_regexp__regex_i_u_
to
main
May 24, 2026 13:21
graphite-app
Bot
deleted the
05-22-feate_linter_no-misleading-character-class_add_suggestions_for_regex_literal
branch
Dunqing
added a commit
that referenced
this pull request
May 26, 2026
# Oxlint ### 🚀 Features - 10da26b linter: `no-misleading-character-class` add suggestions for regex literal (#22681) (Sysix) - b84941e linter/vue: Implement no-expose-after-await rule (#22675) (bab) - 98b98c1 linter/vue: Implement no-computed-properties-in-data rule (#22674) (bab) - 868e2e8 linter: Add suggestion for `no-misleading-character-class` (#22631) (Sysix) - 2d4c919 oxlint: Support `vite-plus/resolveConfig` for vite.config.ts (#22456) (leaysgur) - 2a60012 linter/vue: Implement require-render-return rule (#22613) (bab) - 9f227fd linter/vue: Implement no-deprecated-props-default-this rule (#21892) (bab) - 9cd28b3 linter: Add debug option to print files to be linted (#22546) (camchenry) - 87f065e linter/vue: Implement return-in-emits-validator rule (#21935) (bab) - ea0380c linter/unicorn: Implement `import-style` rule (#22173) (Hao Chen) - dde40fe linter/vue: Implement no-watch-after-await rule (#22006) (bab) - a735eb0 linter/vue: Implement valid-next-tick rule (#22531) (bab) - 6dc615d linter/vue: Implement no-shared-component-data rule (#21842) (bab) - a656418 linter/vue: Implement valid-define-options rule (#22107) (bab) - bb6f1b2 linter/vue: Implement require-slots-as-functions rule (#22244) (bab) - 5fa4774 linter/n: Implement `callback-return` rule (#22470) (Mikhail Baev) ### 🐛 Bug Fixes - 52bd016 linter: Respect allow unused disable directives in LSP (#22715) (camc314) - fa7c463 semantic: Correct TS enum member symbol spans (#22689) (camc314) - ed445ba linter: Respect flags overrides for `RegExp(/regex/i, "u")` (#22678) (Sysix) - 26b9396 semantic: Resolve parameter decorators outside parameter scope (#22623) (camc314) - 203952d linter: `no-misleading-character-class` fix `is_unicode_code_point_escape` check (#22655) (Sysix) - 2f64d3d linter: `no-misleading-character-class` own diagnostic for surrogate pairs without u flag (#22654) (Sysix) - 0c6ebc2 linter/eslint/no-lone-blocks: Do not flag empty loops (#22649) (Mikhail Baev) - 2a7562e linter/no-focused-tests: Mark fixer as a suggestion (#22645) (camc314) - dbe644f linter: Respect args none for unused rest parameters (#22627) (camc314) - d0211b0 linter: Allow undefined in DummyRuleMap index (#22626) (camc314) - 36fc0ec oxlint/lsp: "ignore this" actions merge with existing directive (#22604) (Sysix) - f7f370e linter/vitest/prefer-expect-type-of: Recommend `toBeTypeOf` instead of `expectTypeOf` (#22612) (Mikhail Baev) - 77063e5 linter/consistent-indexed-object-style: Preserve interface modifiers in fixes (#22579) (camc314) - 4f33aa7 linter: Treat `TSGlobalDeclaration` as ambient in `has_ambient_typescript_ancestor` (#22577) (camc314) ### ⚡ Performance - c22938d linter/no-async-endpoint-handlers: Populate node types (#22601) (camc314) - 607486e linter/no-negated-condition: Populate node types (#22602) (camc314) - 4dcaa59 linter/consistent-type-imports: Populate node types (#22600) (camc314) - 5bd3b25 linter/no-unused-vars: Avoid cloned ancestor iterator (#22598) (camc314) - 97fe9ba linter/no-extra-non-null-assertion: Reduce node matches (#22588) (camc314) - ae98296 linter/consistent-indexed-object-style: Populate node types (#22578) (camc314) # Oxfmt ### 🚀 Features - 16b8058 oxfmt: Support `vite-plus/resolveConfig` for vite.config.ts (#22454) (leaysgur) ### 🐛 Bug Fixes - 5a26479 formatter: Preserve import phases (#22692) (Cameron) ### ⚡ Performance - 78cf83f formatter: Pre-size output buffer using source text length (#22594) (Dunqing) Co-authored-by: Dunqing <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds fixer suggestions for
no-misleading-character-classwhen the offending pattern comes from a RegExp literal (either standalone/.../or passed as the first argument toRegExp(...)/new RegExp(...)). This aligns the rule’s autofix behavior across literal and constructor forms by validating patterns with the correct parser for each input kind.Changes:
u-flag suggestion forAstKind::RegExpLiteralby appendinguto the literal when the pattern is valid under Unicode mode.LiteralParserrather thanConstructorParser).