# SonarLint for VS Code 3.18 - Security Hotspots for SonarCloud users, better code examples display

**URL:** <https://community.sonarsource.com/t/sonarlint-for-vs-code-3-18-security-hotspots-for-sonarcloud-users-better-code-examples-display/91400>\
**Category:** Releases\
**Tags:** python, typescript, vscode, java\
**Created:** [May 24, 2023, 1:40pm UTC](https://community.sonarsource.com/t/sonarlint-for-vs-code-3-18-security-hotspots-for-sonarcloud-users-better-code-examples-display/91400 "2023-05-24T13:40:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marco\_Comi](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/marco_comi/32/14877_2.png) [@Marco\_Comi](https://community.sonarsource.com/u/Marco_Comi)\
**Post date:** [May 24, 2023, 1:40pm UTC](https://community.sonarsource.com/t/sonarlint-for-vs-code-3-18-security-hotspots-for-sonarcloud-users-better-code-examples-display/91400/1 "2023-05-24T13:40:29Z")

</div>

Hello,  
at the beginning of this year, [we introduced](https://community.sonarsource.com/t/sonarlint-for-vscode-3-14-security-hotspots-in-the-ide/82829) the capability for SonarLint to report Security Hotspots directly in your IDE, with an initial focus on those of you using SonarLint together with SonarQube.

We’ve now expanded the support for **Security Hotspots** to **SonarCloud users** as well; basically all of you using SonarLint in connected mode will now see Security Hotspots reported directly in VS Code (reminder: for SonarQube, the minimum version is 9.7).

Something we’ve also added this month is the possibility to have a list of unreviewed Security Hotspots beyond the boundaries of the file you’re currently working on. In fact with version 3.18, if you select the “_In Whole Folder_” option SonarLint will scan every file in the folder you’ve currently opened in VS Code, so that you have a chance to **review all pending hotspots at once** :

![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/6/6/66c024391193d24bf8d71c4434963e9fed53242c.png)

Activating this mode may have a significant performance impact depending on the size and configuration of your projects - so I suggest you have a look at [this wiki page](https://github.com/SonarSource/sonarlint-vscode/wiki/security-hotspots#reporting-security-hotspots-in-the-whole-folder) first 😉

**SPOILER** : We’re also working on the possibility for you to set the output of a hotspot review directly in SonarLint - this will avoid you having to switch between SonarLint and SonarQube/SonarCloud during the review process, stay tuned…

In this release, we’ve also made further improvements to our rule descriptions: to help you easily understand and act on the **noncompliant/compliant code examples** : we’ve added **syntax highlighting** to all examples:

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/9/5/95249d8ea4f29a49835ffbaaf1ebeba5aed8d680.png)

For some rules you’ll also find **code diff** highlighting between non-compliant and compliant code examples in our rule descriptions - this will be progressively made available for all rules.

Finally, here is a selection of the new detections we’ve added in our analyzers this month:

- a new [**Java** rule](https://rules.sonarsource.com/java/RSPEC-6485) that advises to use when appropriate the static methods introduced in Java 19 to initialize hash-based collections in order to allocate the requested capacity at construction time
- several new rules for **TypeScript** (more details [here](https://github.com/SonarSource/SonarJS/releases/tag/10.2.0.21568))
- 6 new **Python** rules for the Django framework and 3 new quick fixes (more details [here](https://github.com/SonarSource/sonar-python/releases/tag/4.3.0.11660))

You can read more in the [release notes](https://sonarsource.atlassian.net/browse/SLVSCODE-440?jql=project%20%3D%2010121%20AND%20fixVersion%3D14110%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC).  
Enjoy,

Marco

---

<div class="post-metadata">

**Author:** ![sam-nash](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sam-nash/32/45308_2.png) [@sam-nash](https://community.sonarsource.com/u/sam-nash)\
**Post date:** [May 30, 2023, 11:14am UTC](https://community.sonarsource.com/t/sonarlint-for-vs-code-3-18-security-hotspots-for-sonarcloud-users-better-code-examples-display/91400/2 "2023-05-30T11:14:19Z")

</div>

Are cobol, copybook supported in sonarlint scans.

---

<div class="post-metadata">

**Author:** ![Marco\_Comi](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/marco_comi/32/14877_2.png) [@Marco\_Comi](https://community.sonarsource.com/u/Marco_Comi)\
**Post date:** [June 6, 2023, 1:08pm UTC](https://community.sonarsource.com/t/sonarlint-for-vs-code-3-18-security-hotspots-for-sonarcloud-users-better-code-examples-display/91400/3 "2023-06-06T13:08:43Z")

</div>

Hi @sam-nash, this topic is discussed in [this thread.](https://community.sonarsource.com/t/cobol-support-for-sonarlint-extension-for-vs-code/43950)
