Incorrect issue category

Hi all!

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:

“no-console”: [“warn”, { allow: [“error”] }] no-console - ESLint

and our sonar analysis reports this:

while we were expecting these messages to be classified into code smells category.

Do you have any suggestion or idea about why are classified into bug category?

Thanks in advance.


Welcome to the community!

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.


Hi Ann,

the version is Community Edition - Version 7.4.

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?

Kind regards,

Hi Alvaro,

(Sorry for the missing accent; AmE keyboard :flushed: )

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:

7.4 → 7.9.6 → 8.9.10 → 9.9.4 → 10.5.1 (last step optional)

You may find these resources helpful:

If you have questions about upgrading, feel free to open a new thread for that here.

Regarding your question, all bets are off on a version that old and I simply can’t help you.