Roadmap

Here are some of the big topics that we will cherish throughout 2018, on top of continuously improving the user experience, and refining features so that SonarLint always help you fix issues before they exist.

Focus on rules and issues that matter to you

Out-of-the-box, we want SonarLint to remain as simple and powerful as possible, so that you can focus on your coding. In the same spirit, if you think there are a few coding rules or issues that do not apply to your specific case, then we want you to be in control and use SonarLint to its full extent, to avoid any disturbance. That includes:

• excluding specific files from SonarLint analysis
• deactivating specific rules that are not valuable to you
• muting specific issues that you deem as not-applicable
• enabling non-default rules that you would like to be checked as you code

This should be available to all developers across all IDEs supported by SonarLint.

Feature parity, across all IDEs

VSCode and Atom are the latest joiners in the SonarLint-supported family. For those IDEs, SonarLint may not offer all the features and capabilities it provides in other IDEs, however we definitely intend to get there! Connected Mode just arrived in SonarLint for VS Code, and altogether we constantly focus on avoiding feature-gap between IDEs. We really want all developers, irrespectively of the language and IDE they code in, to benefit from the full feature-set of SonarLint.

End-to-end experience for SonarQube and SonarCloud users

The Connected Mode unlocks great integrations with SonarQube/SonarCloud, so that the issues reported in your IDE are in-line with the project health and Quality Gate that your team is tracking. As more features make it to SonarQube/SonarCloud, we want to make sure that SonarLint is integrated with that whenever it provides value. For example, just think of SonarLint detecting the branch you’re working on, and aligning its code analysis with what is reported in SonarQube/SonarCloud (now supporting branch and PR analysis).