Make sure ESLint doesn't fail with invalid JS (syntax_error rule) #52
Assignees
Labels
Comments
tofumatt
added a commit
that referenced
this issue
Oct 7, 2015
Adds a test case for malformed JS and a bit of extra code in the JS Scanner to make sure we handle SyntaxErrors, which are a bit different from other errors created by ESLint. Fixes #52.
tofumatt
added a commit
that referenced
this issue
Oct 8, 2015
Adds a test case for malformed JS and a bit of extra code in the JS Scanner to make sure we handle SyntaxErrors, which are a bit different from other errors created by ESLint. Fixes #52.
tofumatt
added a commit
that referenced
this issue
Oct 8, 2015
Adds a test case for malformed JS and a bit of extra code in the JS Scanner to make sure we handle SyntaxErrors, which are a bit different from other errors created by ESLint. Fixes #52.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a test case I hadn't considered in #44; I'll leave it here as a separate bug.
We should be sure bad JS like:
doesn't crash the validator.
Turns out this is the
syntax_errorrule. This is a good one to implement early I think.The text was updated successfully, but these errors were encountered: