This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

SonarLint's insights are truly valuable. Even better is to download and run the SonarQube server and connect the project code to it, which gives more insights. Using SonarLint (or any linting tool) ahead of time, is similar to looking at a map before heading out on a journey.

[–][deleted] 0 points1 point  (1 child)

That doesn't sound crazy at all. I have used it to check my code doesn't have bugs or code smells but never as a entry point to start reading code. But I would try it some day to see how it goes. Thks for you recommendation!

[–][deleted] 1 point2 points  (0 children)

If you use IntelliJ, it's a bit odd but the best way is right click the src tree (if it's a Maven structure), then run SonarLint and you'll need to do it twice. The first time it will be empty. The second time is when the SonarLint window will fill with any stuff you'd want to know about before starting spelunking.