You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ES2025 now allows duplicate named capturing groups.
But using numbers to backreference them seems very hard to read and misleading, so I'd like to add a rule to disallow that.
Description
The new rule will flag as an error if a numbered backreference refers to a duplicate named capturing group.
Examples
/* ✓ GOOD *//^(?:(?<foo>a)|(?<foo>b))\k<foo>$/u.test('aa');// true/^(?:(?<foo>a)|(?<foo>b))\k<foo>$/u.test('bb');// true/* ✗ BAD *//^(?:(?<foo>a)|(?<foo>b))\1$/u.test('aa');// true/^(?:(?<foo>a)|(?<foo>b))\1$/u.test('bb');// false
Maybe there's a better rule name 🤔
The text was updated successfully, but these errors were encountered:
Hmm... I think the purpose is a bit different from prefer-named-backreference, which always recommends named backreferences, because we don't know whether users should change backreferences or rename named capturing groups in response to the new rule report.
Motivation
ES2025 now allows duplicate named capturing groups.
But using numbers to backreference them seems very hard to read and misleading, so I'd like to add a rule to disallow that.
Description
The new rule will flag as an error if a numbered backreference refers to a duplicate named capturing group.
Examples
Maybe there's a better rule name 🤔
The text was updated successfully, but these errors were encountered: