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

Update: improve null detection in eqeqeq for ES6 regexes (fixes #8020) #8042

Merged
merged 3 commits into from Feb 11, 2017

Conversation

not-an-aardvark
Copy link
Member

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

[x] Bug fix (see #8020)

What changes did you make? (Give an overview)

This fixes the detection of null literals in eqeqeq, to prevent it from treating unicode/sticky regexes like null in Node 4. When parsing values that cannot be represented in the current environment (e.g. unicode regexes in Node 4), the result is a Literal node with node.value === null. The eqeqeq rule assumed that any literal node with node.value === null is a null literal.

This also adds a isNullLiteral function to ast-utils.js to prevent other rules from making the same mistake.

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

Nothing in particular

@not-an-aardvark not-an-aardvark added accepted There is consensus among the team that this change meets the criteria for inclusion bug ESLint is working incorrectly rule Relates to ESLint's core rules labels Feb 8, 2017
@mention-bot
Copy link

@not-an-aardvark, thanks for your PR! By analyzing the history of the files in this pull request, we identified @mysticatea, @gyandeeps and @platinumazure to be potential reviewers.

Copy link
Member

@mysticatea mysticatea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

Copy link
Member

@mysticatea mysticatea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I re-thought this.
node.raw property does not exist in ESTree spec.
Can we use it safely?

@not-an-aardvark
Copy link
Member Author

Oh, I hadn't realized that. I suppose I can check !node.regex instead.

@eslintbot
Copy link

LGTM

@not-an-aardvark not-an-aardvark merged commit 90fd555 into master Feb 11, 2017
@not-an-aardvark not-an-aardvark deleted the eqeqeq-unicode-regexes branch February 11, 2017 02:03
@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Feb 6, 2018
@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 Feb 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted There is consensus among the team that this change meets the criteria for inclusion archived due to age This issue has been archived; please open a new issue for any further discussion bug ESLint is working incorrectly rule Relates to ESLint's core rules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants