SonarLint still checks disabled rule after configuring in SonarQube

Please provide

  • Operating system: Windows 11
  • SonarLint plugin version: v4.5.1
  • Programming language you’re coding in: TypeScript and c#
  • Is connected mode used:
    • Connected to SonarQube (and which version): 10.4.1


I’m using SonarLint in connected mode with SonarQube, and I would like to disable a rule in SonarQube so that this rule is no longer checked during development in VS Code.

In SonarQube, I have already made a copy of a Quality Profile and manually configured a specific profile to add the language to the project.

After this process, I disabled a specific rule (Rule ID: typescript:S1135), but when using SonarLint in connected mode in VS Code, the rule continues to be checked. Why does this happen?

Is the procedure I performed correct, or did I fail somewhere in the process?


Welcome to the community!

Did you run a new analysis, server-side, after you disabled the rule? My memory is a little hazy on this point, but I believe SonarLint uses the profile/rules that were applied in the last SonarQube analysis. I suppose that’s so that the results you see in SonarLint match the ones you see in SonarQube.

Can you make sure a new SonarQube analysis has been run and see if this is still a problem?


Hi Ann,

Thank you for your response and the valuable insight.

I followed your suggestion and ran a new analysis on my project in SonarQube. However, despite disabling the rule, SonarLint is still indicating the alert for the rule that I deactivated.

I’m wondering if there might be another factor at play here causing this discrepancy between SonarQube and SonarLint. Do you have any further suggestions on how to troubleshoot this issue?

Thanks again for your help.

Best regards,

Hi honurb,

Has SonarLint been restarted in between then and now?