SonarLint for Visual Studio Code
How it works
Simply open a INT, MAC, CLS or JS file, start coding, and you will start seeing issues reported by SonarLint. Issues are highlighted in your code, and also listed in the 'Problems' panel.
You can access the detailed rule description directly from your editor, using the provided contextual menu.
Check the rules to see what SonarLint can do for you:
The only thing you need is a Java Runtime (JRE) 8 installed on your computer.
SonarLint should automatically find it but you can also explicitly set the path where the JRE is installed using the 'sonarlint.ls.javaHome' variable in VS Code settings. For example:
You can connect SonarLint to SonarQube >= 5.6 or SonarCloud to benefit from the same rules and settings that are used to inspect your project on the server. SonarLint then hides in VSCode the issues that are marked as Won’t Fix or False Positive.
To configure the connection, have a look at SonarLint in default user settings.
If you change something on the server such as the quality profile, you can trigger an update of the local cache using the "Update SonarLint binding to SonarQube/SonarCloud" command on the command palette (search for "sonarlint").
For security reasons, the token should not be stored in SCM with workspace settings.
Contributions and license
SonarLint for Visual Studio Code is open source under the LGPL v3 license. Feel free to submit Pull Requests.
The preferred way to discuss about VS SonarLint for CacheQuality is by posting on the Project Issues tab. Feel free to ask questions, report issues, and give suggestions.