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
Parser is confused about delete statement #387
Comments
I think the automatic semicolon insertion should be one part, the new parser has to implement exactly as defined in ecma standard ;) |
I'm having some issues with this:
I get these errors. Just wanted to make sure that makes sense:
I have asi turned to true. |
I have and it throws "Expected an operator and instead saw 'delete'." What should be a better way of writing this statement? |
Curios about this one myself. |
+1 |
This is rather annoying. |
affected by this also. Is there a workaround? |
@danmilon prefix your delete statements with |
That will obviously not trigger the bug, but still, uglifying my code to silent jshint is not appropriate. I will try to parse the output, identify the errors caused by this bug, and clear them out. Do you know if this is fixed on master? |
@danmilon as far as I know it's not. Right now I make my code ugly to satisfy jshint as I rarely use the |
Closing this as wontfix for this tree. Too much PITA to fix and is not a problem in Next. |
@antonkovalyov what do you mean its not a problem in Next? |
Next uses Esprima as its JavaScript parser and Esprima can handle any valid ES5 code. |
This is Next btw |
Any news on this? It's still a problem. |
Still facing the same, any news on this, will it be fixed ? |
@antonkovalyov Thoughts on re-opening this bug? |
+1 |
1 similar comment
👍 |
@antonkovalyov This is still a problem in the latest version, v1.1.0 - are you saying that this version does not have the code from Next yet? Over at Next it says that it has now been merged into the main repository, so it's unclear what we should do. How do we get around this issue? It's quite annoying. |
+1 |
@antonkovalyov still an issue here. 👍 |
Still an issue for me as well with 2.1.2 |
@antonkovalyov Can you please reopen this? Or should we file a new issue? |
Just a quick heads-up. I ended up having to fix this very issue in a patch I did to get jshint to parse I should have a pull request up by tomorrow. |
Also fixed jshint#387. Also fixed jshint#1108.
It tells me I shouldn't delete variables, that's fine.
However,
Makes the parser all confused.
3 3 'Expected an operator and instead saw 'delete'.'
3 9 'Missing semicolon.'
3 10 'Expected an assignment or function call and instead saw an expression.'
The text was updated successfully, but these errors were encountered: