Enforce `.replaceAll()` over `.split().join()` in `prefer-string-replace-all` rule

描述

foo.split('a').join('b');

foo.replaceAll('a', 'b');

// Not sure about this, maybe add `g` flag, result the same?
foo.split(/a+/).join('b');

// Different with foo.replaceAll('', 'b');
foo.split('').join('b');

贡献者指南

技术栈

javascriptnodejs

领域

toolingdeveloper experience

议题类型

feature

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

half day

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

fresh

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

familiarity with ESLint rulesAST manipulationJavaScript

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

40

研究方向

Examine the existing rule implementation in the eslint plugin unicorn repository, specifically the `prefer string replace all` rule file (`rules/prefer string replace all.js`). Understand how the rule currently detects `.replaceAll()` usage and how to add detection for `.split().join()` patterns. Review the test file for that rule to see existing test cases. Consider edge cases like using regex or empty string in split. The issue author suggested that `.split(/a+/).join('b')` might be equivalent, while `.split('').join('b')` is different. Investigate these and implement the check.