Hi,
Yes, if you look at the SonarLint output, after enabling verbose logs, you should see this each time an analysis is triggered:
[Debug - 15:30:04.757] Analysis triggered on 'file:///home/julien/Prog/Projects/sonarlint/sonarlint-vscode/scripts/prepare.js' with configuration:
[
projectKey: org.sonarsource.sonarlint.vscode:sonarlint-vscode
baseDir: /home/julien/Prog/Projects/sonarlint/sonarlint-vscode
extraProperties: {}
inputFiles: [
file:///home/julien/Prog/Projects/sonarlint/sonarlint-vscode/scripts/prepare.js (UTF-8) [js]
]
]
The presence of the projectKey attribute is a confirmation the connected mode is used.
Connected mode is not reaching the server continuously. It is only contacting the server to fetch (and cache) some metadata needed to ensure SonarLint analysis will produce similar results than SonarQube/SonarCloud analysis (enabled rules, file exclusions, issue suppresion, …). To “refresh” the local storage of those metadata, you have to manually trigger it (use SonarLint: Update all projects bindings to SonarQube/SonarCloud action).
I agree the documentation is missing here. Only Apex and PL/SQL are added by using connected mode. C is not yet supported, you can follow/vote for:
https://community.sonarsource.com/t/sonarlint-for-vscode-c-c-support/4732