I’m new to sonarQube so sorry if this is a dumb question. Is there a way to link the snippits of code seen in the issues tab to the actual code, either via an editor or something? Some of the code displayed looks wrong but you have to find the definition of the structure or class to be sure - there is not a way just to click on it and bring it up? I think Coverity and Code Sonar have that capability.
We have that built in for Security Hotspot review if you’re also using SonarLint, but not for other issues.
Since issues are presented in the context of the code, with file name and line numbers, I’m a little confused. Can you explain why that context isn’t enough?
I’d like the convenience to triage the problems only using the Code Sonar server for a couple of reasons.
- I may not have the code locally on my machine if the scan was run by a different developer.
- The path may not be the same on my machine, so I have to search for the file and code, which takes time.
- The version of code on my local machine may be different that the version that the scan was run on.
Triaging is the most time consuming, so anything that can be done to speed that up and not have to spend a lot of time cross referencing code would be VERY helpful.
So you’re expecting a link to… the right version of the right file in GitHub, e.g.?
That would be handy - or more code from the snippet, like the applicable structure or class if it is referring to it. I thought other static anlysis tools you could hover over a structure, function name, class, and see it’s definition.
So you’re looking for the IDE-like functionality of being able to see or jump to the definition in another file?