SonarLint review by a Hybris Developer
Use Cases and Deployment Scope
We use SonarLint in our project to check all the issues we get in our code quality report in the eclipse itself without having to run our server up again and to do every time a new build when we make any change to fix that. We install SonarLint in our eclipse from Eclipse Marketplace and then when we generate the code quality report and it shows any issues in it, like bugs, vulnerabilities, code refactoring, etc. then we need to fix those issues with the help of SonarLint.
Generally to fix these issues, first we have to do the code changes in our local create a fresh build and generate a new code quality report every time to check if the issue is fixed or still persists. But if we use SonarLint, then we can see all the issues in our local only, the code piece which is having issue is highlighted with blue lining as soon as we load the file, and when we do any fix to resolve the issue, we can just see that in our local if it worked or not just by saving the file, there is even no need to do a fresh build or create a new code quality report, if the blue lining gets removed from the code piece which was having issue after the SonarLint processing as soon as we save the file, then we can confirm if the issue is fixed or not. SonarLint saves a lot of time of doing build and generating fresh code quality report each and every time for the code issues.
Pros
- SonarLint highlights all the issues in our codes and also displays the severity of each issue.
- SonarLint also provides suggestions for how to fix those code issues which are highlighted.
- SonarLint starts the processing of the file as soon as it is opened and highlights all the issues which it found.
- When we fix the issue, we don't even need to create a new build or generate fresh code quality report, as soon as we save the file with the changes, it does the processing again and shows the result if the issue is fixed or not.
- SonarLint saves a lot of time and effort by saving us from doing fresh build every time and generating new code quality report every time, thus increasing the efficiency and output which is in return beneficial for the client.
Cons
- Sometimes, SonarLint does not highlight the issues in the code correctly.
- The severity of the issues highlighted is according to the default rules set, we should also be given authority to set the severity of the issues.
- The default fixes which SonarLint provides should be more enhanced and there should be more fixes available.
- Sometimes it takes a lot of time for processing of the file when any new file is loaded or changes are saved in a file.
Likelihood to Recommend
