useRegexLiterals

Цей контент ще не доступний вашою мовою.

JavaScript (and super languages)

Summary

Rule available since: v1.3.0
Diagnostic Category: lint/complexity/useRegexLiterals
This rule is recommended, which means is enabled by default.
This rule has a safe fix.
The default severity of this rule is warning.
Sources:
- Same as prefer-regex-literals

How to configure

1
{
2
  "linter": {
3
    "rules": {
4
      "complexity": {
5
        "useRegexLiterals": "error"
6
      }
7
    }
8
  }
9
}

Description

Enforce the use of the regular expression literals instead of the RegExp constructor if possible.

There are two ways to create a regular expression:

Regular expression literals, e.g., /abc/u.
The RegExp constructor function, e.g., new RegExp("abc", "u") .

The constructor function is particularly useful when you want to dynamically generate the pattern, because it takes string arguments.

Using regular expression literals avoids some escaping required in a string literal, and are easier to analyze statically.

Examples

Invalid

1
new RegExp("abc", "u");

code-block.js:1:1 lint/complexity/useRegexLiterals  FIXABLE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Use a regular expression literal instead of the RegExp constructor.
  
  > 1 │ new RegExp(“abc”, “u”);
      │ ^^^^^^^^^^^^^^^^^^^^^^
    2 │ 
  
  ℹ Regular expression literals avoid some escaping required in a string literal, and are easier to analyze statically.
  
  ℹ Safe fix: Use a literal notation instead.
  
    1   │ - new·RegExp(“abc”,·“u”);
      1 │ + /abc/u;
    2 2 │

Valid

1
/abc/u;
2

3
new RegExp("abc", flags);