regexUnicodeProperties

Reports inconsistent Unicode property names in regular expressions.

✅ This rule is included in the ts stylistic presets.

Unicode properties may be expressed in several different ways. Including the fully-written out category prefix is a more verbose way that is not necessary.

This rule detects inconsistent Unicode property names in regular expressions and suggests more idiomatic forms for:

1. Unnecessary gc= / General_Category= prefix: unicode general category properties can be used without the prefix.
2. Long script names: short script aliases like Grek should use the full name Greek for readability.

Examples

Unnecessary General_Category Prefix

❌ Incorrect

const pattern = /\p{gc=L}/u;
const pattern2 = /\p{General_Category=Letter}/u;

✅ Correct

const pattern = /\p{L}/u;
const pattern2 = /\p{Letter}/u;

Short Script Names

❌ Incorrect

const pattern = /\p{sc=Grek}/u;
const pattern2 = /\p{Script=Latn}/u;

✅ Correct

const pattern = /\p{sc=Greek}/u;
const pattern2 = /\p{Script=Latin}/u;

Script_Extensions

❌ Incorrect

const pattern = /\p{scx=Cyrl}/u;

✅ Correct

const pattern = /\p{scx=Cyrillic}/u;

RegExp Constructor

❌ Incorrect

const pattern = new RegExp("\\p{gc=L}", "u");
const pattern2 = new RegExp("\\p{sc=Grek}", "u");

✅ Correct

const pattern = new RegExp("\\p{L}", "u");
const pattern2 = new RegExp("\\p{sc=Greek}", "u");

Options

This rule is not configurable.

When Not To Use It

If your project has a style guide that prefers explicit gc= prefixes or short script names for consistency with other documentation, you might want to disable this rule.

Further Reading

• MDN: Unicode character class escape
• Unicode Technical Standard #18: Unicode Regular Expressions

Equivalents in Other Linters

• ESLint: regexp/unicode-property