Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chore: enable require-unicode-regexp on ESLint codebase #11422

Merged
merged 1 commit into from Feb 22, 2019

Conversation

not-an-aardvark
Copy link
Member

@not-an-aardvark not-an-aardvark commented Feb 21, 2019

What is the purpose of this pull request? (put an "X" next to item)

[x] Other, please explain:

What changes did you make? (Give an overview)

This enables the require-unicode-regexp rule on the ESLint codebase. There were some discussions about possibly adding this rule to eslint:recommended, so I thought it would be worth dogfooding.

This change does not start parsing user-provided unicode regexes with the u flag, because that could be a breaking change. (However, I still think it would be a good idea. I created an issue for it at #11423.)

Is there anything you'd like reviewers to focus on?

These changes were applied by temporarily adding an unsound fixer to the require-unicode-regexp rule, running eslint --fix on the codebase, then removing the fixer before committing.

@not-an-aardvark not-an-aardvark added the chore This change is not user-facing label Feb 21, 2019
@not-an-aardvark not-an-aardvark merged commit 5018378 into master Feb 22, 2019
@not-an-aardvark not-an-aardvark deleted the enable-require-unicode-regexp branch February 22, 2019 01:42
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Aug 22, 2019
@eslint-deprecated eslint-deprecated bot added the archived due to age This issue has been archived; please open a new issue for any further discussion label Aug 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived due to age This issue has been archived; please open a new issue for any further discussion chore This change is not user-facing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants