SonarLint

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.