-
Notifications
You must be signed in to change notification settings - Fork 184
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
Parsing issue with default in export clause specifier #960
Comments
Probably it's due to Flow syntax support #584 (was added in 3.2) |
Is there a way we can temporary tell Sonar to ignore theses exports until the bug is fixed? We have an export like this in hundreds of files, which are not getting analyzed since the update. |
@hcomnetworkers nope :( |
For us, we are only using this syntax in our React |
Still a problem on SonarQube v7.2 (build 13530) and SonarJS 4.1 (build 6085). |
I want to report a bug.
SonarJS version: 4.1 (build 6085)
SonarQube version: Version 6.7 (build 33306)
Rule key: javascript:ParsingError
Logs
Expected behavior
We updated today to the latest Version of SonarJS und after the scan we got multiple parse errors. In the previous it worked as expected - the files got parsed without errors. Unfortunately we don't know our previous version number.
The text was updated successfully, but these errors were encountered: