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

Fix: no-misleading-character-class crash on invalid regex (fixes #12169) #12347

Merged
merged 1 commit into from Oct 25, 2019

Conversation

mdjermanovic
Copy link
Member

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

[X] Bug fix #12169

Tell us about your environment

  • ESLint Version: 6.4.0
  • Node Version: 10.16.0
  • npm Version: 6.9.0

What parser (default, Babel-ESLint, etc.) are you using?

Please show your full configuration:

Configuration
module.exports = {
  parserOptions: {
    ecmaVersion: 2015,
  }
};

What did you do? Please include the actual source code causing the issue.

/* eslint no-misleading-character-class: ["error"] */

var r = new RegExp('[Á] [ ');

What did you expect to happen?

Not to crash.

What actually happened? Please include the actual, raw output from ESLint.

SyntaxError: Invalid regular expression: /[Á] [ /: Unterminated character class
    at RegExpValidator.raise ...

What changes did you make? (Give an overview)

try/catch to ignore invalid regular expressions.

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

The original issue is about regex literals with @typescript-eslint/parser, but the same applies to the regex constructor with the default parser.

I think it isn't necessary to add a @typescript-eslint/parser test since it's testable with the default?

@eslint-deprecated eslint-deprecated bot added the triage An ESLint team member will look at this issue soon label Oct 1, 2019
@mdjermanovic mdjermanovic 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 and removed triage An ESLint team member will look at this issue soon labels Oct 1, 2019
Copy link
Member

@platinumazure platinumazure left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

Copy link
Member

@kaicataldo kaicataldo left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@platinumazure platinumazure merged commit 0bffe95 into master Oct 25, 2019
@platinumazure platinumazure deleted the issue12169 branch October 25, 2019 18:10
@platinumazure
Copy link
Member

Thanks @mdjermanovic for contributing!

@eslint-deprecated eslint-deprecated bot locked and limited conversation to collaborators Apr 24, 2020
@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 Apr 24, 2020
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.

RegExp parse errors in regexpp are not tolerated and crash eslint
3 participants