Programming language you’re coding in:
Java in IntelliJ Idea Ultimate
Is connected mode used:
Connected to SonarCloud or SonarQube (and which version):
connected to SonarQube
Community Edition
Version 7.9.5 (build 38598)
And a thorough description of the problem / question:
I appreciate the possiblity to scan all VCS changes files with one click.
Additionally there this a possiblity to scan files per folder.
Usually I work on Java classes from different folders, but same context.
What I miss are more possibilities to scan groups of files.
On reviews it would be very helpful to scan alle files changed within one or several commits to make sure no new Sonar issues are coming into the code (double eye principle).
I would love to scan with only one click all files opened in Editor in IJ. This is a context I’m working in and it would be helpful to scan them all, even I did not change them.
Open editors could be a compromise used even for reviews of existing commits.
Would like to hear your opinion on that convenience feature!
I’ve moved your topic to Product Manager for a Day. Presumably the PMs will be along soon.
In the meantime, I need to make sure you know your version is past EOL. You should upgrade to either the latest version or the current LTS at your earliest convenience. Your upgrade path is:
7.9.5 → 8.9.10 → 9.8 (last step optional)
(Note that the release of a new LTS, 9.9, is expected on 7 Feb 2023.)
Hi @frankleja and many thanks for your input!
You may already have noticed that as a SonarQube user, at Sonar we promote the Clean As You Code approach, which basically means you can incrementally improve the quality of your code base by simply focusing your efforts on making sure the new code you deliver is clean. This is why for example SonarQube offers dedicated views to show issues on recently modified code only.
We’re definitely going to look into ways to help our users apply the Clean As You Code principles starting in the IDE with SonarLint. For example we are considering to:
provide options to limit the issues displayed by SonarLint to recently modified code; what “recently modified” means is yet to be defined, it could be since the last commit or starting from a user-defined commit for example
when the user is about to commit new code, provide a way to list all the issues that are going to be added to the codebase with that commit, so that the user has a second chance to review and fix them.
I feel those plans resonates well with the following comment you made:
On reviews it would be very helpful to scan alle files changed within one or several commits to make sure no new Sonar issues are coming into the code (double eye principle).
On the other hand, I am curious to understand a little more what benefit you would expect from scanning all files opened in code editors, and what you would like to see at the end of this scan (all issues in those files, or new issues only?). I am also wondering, in case we’ll deliver the two options I’ve mentioned above, would you still have the same need?