-
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
Support parsing of Flow annotations #584
Comments
+1 |
2 similar comments
+1 |
+1 |
+1 |
2 similar comments
+1 |
+1 |
Can sonarjs be used with flow at all? We have a bunch of project that employ flow. Do people configure sonar to use js output from flow maybe? |
@memelet what you propose could work and with source maps it might even be vaguely useful, but do consider that the reason we are not yet supporting flow annotation is not related to parsing them without failing, it's related to the information content they provide : if you are using flow and we run analysis on your sources (or output) without understanding the information provided by flow we might raise a lot of issues that are not relevant. |
@inverno at the moment the scanner cannot parse files annotated with flow. Any files that have flow annotations cause an |
hi, |
@cszczotka I have added flow-remove-types to my project and pointed Sonarqube to scan the non-annotated JS. It's far from ideal and meant to be temporary, but at least the code gets scanned. |
Flow features:
|
Some Links
|
There is still some syntax not supported. See this issue #771 |
Hi, I am still having issues with flow syntax ? Is there a workaround or any updates? Thank you |
Migrated from: https://jira.sonarsource.com/browse/SONARJS-828
Flow: https://flow.org/
The text was updated successfully, but these errors were encountered: