-
-
Notifications
You must be signed in to change notification settings - Fork 1k
📎 Port prefer-regexp-test #9377
Copy link
Copy link
Labels
A-LinterArea: linterArea: linterL-JavaScriptLanguage: JavaScript and super languagesLanguage: JavaScript and super languagesS-FeatureStatus: new feature to implementStatus: new feature to implementS-Help-wantedStatus: you're familiar with the code base and want to help the projectStatus: you're familiar with the code base and want to help the project
Metadata
Metadata
Assignees
Labels
A-LinterArea: linterArea: linterL-JavaScriptLanguage: JavaScript and super languagesLanguage: JavaScript and super languagesS-FeatureStatus: new feature to implementStatus: new feature to implementS-Help-wantedStatus: you're familiar with the code base and want to help the projectStatus: you're familiar with the code base and want to help the project
Type
Fields
Give feedbackNo fields configured for Task.
Description
Can take a lot of inspiration from
useRegexpExec. These 2 might be a little confusing, as if this one is more advanced, but the use-case between these is different. This rule is meant for when the output is used in a boolean setting, while the other rule is meant for querrying. Good to make this clear in the description of the ruleName suggestions:
useRegexpTestWant to contribute? Let us know you are interested! We will assign you to the issue to prevent several people to work on the same issue. Don't worry, we can unassign you later if you are no longer interested in the issue! Read our contributing guide and analyzer contributing guide.