Facing issue on sonarlint warning errors were not shown for specific rule in VS-code

SonarLint
, ,
1

I implemented sonarlint on my vscode it was able to connect with sonarqube using connected mode and it was working all the rule and showing sonarlint warning errors except the one rule.

+++
Rule failing

“===” and “!==” should be used instead of “==” and “!=”
Code Smell
Major

suspicious
Available Since
May 12, 2020
SonarQube (TypeScript)
Constant/issue: 5min
The == and != operators do type coercion before comparing values. This is bad because it can mask type errors. For example, it evaluates ’ \t\r\n’ == 0 as true.

It is best to always use the side-effect-less === and !== operators instead.

Noncompliant Code Example
if (var == ‘howdy’) {…} // Noncompliant
Compliant Solution
if (var === ‘howdy’) {…}
Exceptions
Even if testing the equality of a variable against null doesn’t do exactly what most JavaScript developers believe, usage of == or != is tolerated in such context. In the following case, if foo hasn’t been initialized, its default value is not null but undefined. Nevertheless undefined == null, so JavaScript developers get the expected behavior.

if(foo == null) {…}

+++

These are my tools version in my local I used for installation.
+++
java version - 17.0.11
node version - v18.20.3
vscode version - 1.90.2
sonarlint version - v4.6.0
+++

Can I have any clue to resolve this issue and want to show sonarlint warning errors for this rule?

2

Hey there.

S1440 is not in the built-in (default) Sonar Way. This is the QP that SonarLint uses by default if not bound to a specific project.

Are you sure a Quality Profile with this rule enabled is being used for this project? You can check the logs:

3

Yes, I am sure that this rule is enabled and being used for this project.
We have the custom quality profile as default as configured to this.
Is that possibility that java 17.0.11 version is not supporting this specific rule behaviors in VS-code?

Because this rule is working in sonarqube and showing the error on sonarqube.
But in vscode it is not showing the error for this particular rule.

4

Did you check the SonarLint logs like I mentioned?