Please provide
- Operating system:
- ProductName: macOS
- ProductVersion: 15.7
- BuildVersion: 24G222
- SonarQube for VS Code plugin version: 4.33.0
- Programming language you’re coding in: Vue 3 - Typescript
- Is connected mode used:
- SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?):
- Connected to SonarQube Server
And a thorough description of the problem / question:
Hello team,
I’m using the SonarQube for IDE extension in VS Code for a Vue 3 + TypeScript project.
The extension is generally working fine — several rules are being correctly detected and highlighted.
However, I’ve noticed that the rule Nullish coalescing should be preferred (typescript:S6606) is not highlighted in the IDE, even though:
-
It is active in my SonarQube Quality Profile.
-
It appears in the IDE rule list.
-
It is correctly detected on the SonarQube server during full analysis.
I have verified that my IDE project is connected to the SonarQube server (bound project mode).
Other rules (e.g., code style, unused variables, etc.) are being detected properly in the same files.
Interestingly, one of my colleagues using PhpStorm is able to see this specific issue highlighted correctly in their IDE.
Example:
The following should be flagged but isn’t:
const w: number | null = 0;
const width = w || DEFAULT_PAGE_SECTION_COLUMN_WIDTH_PT;
pageSection.meta?.width || DEFAULT_PAGE_SECTION_COLUMN_WIDTH_PT;
No issue is shown in VS Code, though the same code raises a warning on the SonarQube server.
Additional Question:
Is there a way in VS Code to view all SonarQube issues across the project — similar to how PhpStorm shows issue counts per file in the sidebar — without having to open each file individually?
Currently, it seems I can only see issues after opening files, whereas PhpStorm displays them globally.
Thank you for your help in clarifying this behavior.
Best regards,
