Rule Change: Suggestions for `require-unicode-regexp`
See original GitHub issueWhat rule do you want to change?
require-unicode-regexp
What change to do you want to make?
Implement suggestions
How do you think the change should be implemented?
A new default behavior
Example code
/abc/
What does the rule currently do for this code?
Reports error
What will the rule do after it’s changed?
Give user suggestion prompt to convert into:
/abc/u
Participation
- I am willing to submit a pull request to implement this change.
Additional comments
N/A
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:17 (16 by maintainers)
Top Results From Across the Web
require-unicode-regexp - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >regexp/require-unicode-regexp | eslint-plugin-regexp
This rule reports regular expressions without the u flag. It will automatically add the u flag to regular expression where it is statically ......
Read more >UTS #18: Unicode Regular Expressions
Level 1 is the minimally useful level of support for Unicode. All regex implementations dealing with Unicode should be at least at Level...
Read more >How can I use Unicode-aware regular expressions in ...
The ECMAScript language specification, edition 6 (also commonly known as ES2015), includes Unicode-aware regular expressions. Support must be ...
Read more >Regular expression syntax cheatsheet - JavaScript | MDN
Inside a character class, the dot loses its special meaning and matches a literal dot. Note that the m multiline flag doesn't change...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This seems like a risky thing to autofix. Maybe a suggestion would be better?
Isn’t that implied?