Does the extension support local rust lints in connected mode

SonarQube for IDE VS Code
1

Please provide

  • Operating system: Alma Linux
  • SonarQube for VS Code plugin version: 4.44.0
  • Programming language you’re coding in: Rust
  • Is connected mode used:
    • SonarQube Cloud

And a thorough description of the problem / question:

Does the vscode extension support local lints for Rust? I have the project connected, where a set of rust rules exists cloud side for the project,

"sonarlint.pathToNodeExecutable": "node",
    "sonarlint.connectedMode.project": {
        "connectionId": "foo",
        "projectKey": "foo_bar"
    }
}

.sonarlint/connectedMode.json

{
    "sonarCloudOrganization": "foo",
    "projectKey": "foo_bar",
    "region": "RG"
}

I’m getting lints for languages with default support, but even when running analysis on files where issues are present cloud side, locally sonarqube is reporting nothing on rust files. I don’t see any options in the configuration to point it to a rust analyzer or cargo instance, but it’s not listing any errors in the debug logs

2

Hey @sinceretapir,

SonarQube for IDE, the VS Code plug-in as well the other flavors do not support Rust yet. This means that also in Connected Mode no rules and their issues are synched from SonarQube Cloud to the local IDE as the language plug-in itself is not loaded.

You can have a look at the roadmap and leave feedback for it to be taken into consideration!

Cheers :baby_bottle: