SonarLint for VS Code 3.21 - Clean Code attributes, more secret detections, change issues status

Hello VS Code users,

The main focus of this new release is to reflect our updated vision of Clean Code; you can read more about this important change in Sonar products here.

One of the more visible changes you’ll notice is that for each issue raised in your code, SonarLint reports the associated Clean Code attribute and the Software qualities that are impacted. You can learn more about those definitions here.

Another improvement that we’ve shipped in this release concerns those of you using SonarQube: In SonarLint version 3.19 we added the possibility to change the status of issues that you’re not going to fix. With version 3.21, we have extended this capability to issues that have been detected by SonarLint in new code that has not yet been analyzed by SonarQube. In order to benefit from this, your organization will need to upgrade SonarQube to the 10.2 version, which will be available in a few days.

More great news for Cobol developers: We announced a couple of months ago the support of Cobol analysis in Beta; considering the feedback we’ve received from some of you (and we thank you for that! :pray:), Cobol support is now out of Beta and officially part of the languages supported by SonarLint for VS Code! :partying_face:

In order to help you keep your secrets (tokens, passwords, API keys) secure, this version adds the capability to detect secrets for 22 more popular cloud applications and providers, you can see the full list of supported rules here.

Here is a selection of the other changes:

More information is in the release notes.


A post was split to a new topic: Is there an extra cost to support Cobol on Sonar Lint?