Dear VSCode users,
at Sonar we are working to make the SonarLint connected mode setup a no-brainer for all developers working in a team, so that all team members can align around the same Clean Code standards. This is why we recently introduced a UI to help you set up a connection and project bindings to SonarQube or SonarCloud.
With the 3.10 release, we went one step further and SonarLint is now able to automatically suggest you to bind your local folders to remote projects analyzed by a SonarQube instance or within a SonarCloud organization that you are connected to.
How does it work? It’s quite simple: when you open a project or a folder in VSCode, SonarLint will try to evaluate whether it corresponds to any of the projects available in the existing SonarQube and SonarCloud connections, based on the similarity of the folder names or by the presence of sonar-project.properties or .sonarcloud.properties configuration files in your local directory.
Of course, you can accept or reject the suggestion:
Also, if you code in Python, this new release comes with new rules to ensure the quality of your unit test code.
You can find the full release notes here.
Don’t hesitate to try those new features and let us know what you think.