We are trying to integrate eslint with our Sonar. The team has agreed a set of rules based on different need and once we have run the analysis and we have imported it to sonar, we have noticed that some sonar categories don’t match with our rule descriptions. I.e we have defined this rule:
I’m not sure, but I suspect the is about the error classification of the rule/issue. If you want to dig into this further, could you provide your SonarQube versoin? You’ll find it in the footer if you’re not sure.
That said, I should point out that javascript:S106 is a native rule that detects the same thing.
I have been looking for this file in the eslint analysis (eslint -c ${confFilePath} --format json -o lintReport.json) and the given severity to these lines is warn, does not eslint severity match with sonar’s?
Your version is past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:
)