Improve UI for issues where startColumn == endColumn

[jwfx]

Tested with Community Build v25.1.0.102122 and dotnet-sonarscanner 9.0.2

Please improve the rendering in the UI for issues that have startColumn == endColumn during detection.

Issue as displayed in VS

Issues.json scan result

      "results": [
        {
          "ruleId": "IDE0055",
          "level": "note",
          "message": "Fix formatting",
          "locations": [
            {
              "resultFile": {
                "uri": "file:///D:/downloads/SonarQubeSarifRepro/SonarQubeSarifRepro/Program.cs",
                "region": {
                  "startLine": 7,
                  "startColumn": 15,
                  "endLine": 7,
                  "endColumn": 15
                }
              }
            }
          ],
          "properties": {
            "warningLevel": 1
          }
        }
      ],

What the rendering in the UI currently looks like for these type of issues:

What it actually should look like:
(Manually changed endColumn to startColumn + 1 in Issues.json)

[viktor.vorona]

Hello @jwfx, thank you for the report.
I was not able to fully reproduce the issue. For me the issue appears at least on the correct line.

However since even in my example it is not clear where is the issue and I admit that I could have screwed up somewhere while hacking the conditions to reproduce the bug, I created a ticket to improve this behavior. SONAR-24333

Meanwhile if you could try to reproduce this bug on the latest Community Build (specifically the fact that issue appears on top of the file instead of the correct line) it would be helpful to know that this behavior was not fixed by some side effect.

Anyway my team will take a look at this issue when we’ll have time for it.

[jwfx]

Hi @viktor.vorona

I’ve pushed a minimal repro to GitHub:

GitHub - jwfx/SonarQubeSarifRepro

When I run RunSonarQubeScan.cmd (add your token and url) the result looks like this:

Tested with:

• Community Build v25.2.0.102705
• dotnet-sonarscanner 9.1.0

[viktor.vorona]

Hey @jwfx,

Thank you very much for the repro, thats awesome! It actually made it clear to me that there is another issue on how dotnet sonarscanner works. Basically when the issue has startcolumn == endcolumn and startline == endline this information is not populated when the data comes to Frontend.

So to sum up there are 2 problems:

1. Frontend is not doing the best job on handling startcolumn==endcolumn cases (it looks like it highlighting the whole line - see my screenshot). My squad will handle this issue and you can check the ticket I share for tracking if you want.
2. It seems like dotnet-sonarscanner ignores region field of Issues.json if startColumn==endColumn. I will ping the squad that owns this part and let them fix that issue.

I would like to appreciate again the time you spent on creating the reproducer, I am pretty sure that I would not notice the second issue without your repro.

Best regards,
Viktor

[jwfx]

Hi @viktor.vorona,

thank you for spending the time looking into this.

I suppose issue 1. is handled in SONAR-24333?

Is point 2. tracked somewhere publicly?

Asking, so I can start stalking future changelogs.

[viktor.vorona]

@jwfx, for issue 1 - yes,
For issue 2 we still need to dig a bit deeper to understand what exact component is ignoring this information in the following chain: scanner → analysis processing → endpoint to get the issues, once we discover the exact component that causing it we will create a ticket and assign it to the correct team and update this thread with a link to created ticket.

[sebastien.marichal]

Hello @jwfx,

First, I would like to thank you for providing a full reproducer! That was very helpful!

I was able to pin down the issue, and it is coming from the C# Analyzer plugin.
We consider any issues with the start location and end location being same as a file level issue.

I have created a ticket in our backlog.
Unfortunately, I cannot share it with you as our backlog is private at the moment.

Have a nice day!