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
Is SonarJs has a rule like eslint's no-undef? #621
Comments
Variables should be declared before they are used seem can't find this issue: someFunctionNotDefined(); var a = 'asd';
export {
b
} |
Non-existent variables should not be referenced can't find the issue var a = 'asd'
export {
b
} |
@shikelong those rules are targeting different cases, you are probably looking for "Variables should be declared explicitly", see : https://sonarcloud.io/organizations/inverno-github/rules#rule_key=javascript%3AS2703 |
The rule "Variables should be declared explicitly" has been activate in my Quality Profile. |
I thought you were targeting implicit declarations, not just general uses of non-existent variables. "Non-existent variables should not be referenced" should be catching that, and it does, just not for export statements. |
http://eslint.org/docs/rules/no-undef
Regards.
The text was updated successfully, but these errors were encountered: