useRegexpExec

JavaScript (and super languages)

摘要

¥Summary

规则生效日期：v2.3.9

¥Rule available since: v2.3.9
诊断类别：lint/nursery/useRegexpExec

¥Diagnostic Category: lint/nursery/useRegexpExec
此规则没有修复方案。

¥This rule doesn’t have a fix.
此规则的默认严重级别为 information。

¥The default severity of this rule is information.
此规则属于以下域：

¥This rule belongs to the following domains:
- project
来源：

¥Sources:
- 与 @typescript-eslint/prefer-regexp-exec 相同
  
  ¥Same as @typescript-eslint/prefer-regexp-exec
- 与 regexp/prefer-regexp-exec 相同
  
  ¥Same as regexp/prefer-regexp-exec

如何配置

¥How to configure

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

描述

¥Description

如果未提供全局标志，则强制使用 RegExp#exec 而不是 String#match。

¥Enforce RegExp#exec over String#match if no global flag is provided.

当正则表达式不包含 g 标志时，String#match 的工作方式与 RegExp#exec 相同。始终使用其中一种方式有助于提高代码可读性。

¥String#match is defined to work the same as RegExp#exec when the regular expression does not include the g flag. Keeping to consistently using one of the two can help improve code readability.

RegExp#exec 的速度可能略快于 String#match；这就是我们选择它作为首选用法的原因。

¥RegExp#exec may also be slightly faster than String#match; this is the reason to choose it as the preferred usage.

示例

¥Examples

无效

¥Invalid

1
'something'.match(/thing/);

/invalid.ts:1:1 lint/nursery/useRegexpExec ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Prefer RegExp#exec() over String#match() when searching within a string.
  
  > 1 │ ‘something’.match(/thing/);
      │ ^^^^^^^^^^^^^^^^^^^^^^^^^^
    2 │ 
  
  ℹ Use RegExp#exec() instead of String#match() for consistent and slightly faster regex matching.

有效

¥Valid

1
/thing/.exec('something');

useRegexpExec

摘要

如何配置

描述

示例

无效

有效

相关链接