Checkstyle VS Sourcetrail

I’m a little out of date with Java, but I believe Checkstyle is currently popular: https://github.com/checkstyle/checkstyle

Another example can be applied to code quality itself. Most static analyzers are configurable. If you tried to set Checkstyle Google configuration to the mature project, you would probably get hundreds or even thousands of errors. You can start with just one rule. Ar first glance, it seems not so important. But after the moment when the configuration reaches the repository, you can be sure that no one else can violate this rule in the future.

Checkstyle: a tool that helps programmers write Java code that adheres to a coding standard: https://github.com/checkstyle/checkstyle

So I was there once, sharing my solution. For my current project I use the java formatter jar, but on my previous work I was using checkstyle, you can get it from here: Checkstyle. Then pass your checkstyle xml format config.

On the coding standards side, use linters like https://github.com/checkstyle/checkstyle and https://github.com/eslint/eslint so you have an automated way to detect some errors and enforce style standards.

The most common approach for CI integration is the Maven checkstyle plugin, and you'd have to specify the coding style rules in the checkstyle.xml file. The github repo for checkstyle has checkstyle.xml configs for Google and Sun.

sem-version java 11 wget https://github.com/checkstyle/checkstyle/releases/download/checkstyle-8.41/checkstyle-8.41-all.jar java -jar checkstyle-8.41-all.jar -c /sun_checks.xml MyFile.java

You can find a configuration file for Google’s Java Style on the checkstyle repository.

Direct JAR which can be taken from Github

Maybe Sourcetrail or SciTools Understand if want it statically.

I mostly really on LSP, some form of recursive grep and Sourcetrail. I find sourcetrail super useful for learning a new project.

Discussion of possible solutions: https://github.com/CoatiSoftware/Sourcetrail/issues/1214

You know, the "all functions have unique distinct names" idea is pretty interesting!

Honestly, that reminds me of the PHP standard library a bit, which feels oriented towards procedural programming at times. Now, the language and the actual implementation of the functions aside, i found that pattern really pleasant to work with, especially since it let me work more in line with functional programming principles as well - pure functions and no global state (even if passing data around was more difficult).

Now, i won't say that the approach fits every project or domain out there, but at the very least having a clear idea of what your code depends on and what's going on inside of your code base is an idea that i still stand by. Sadly, the only tool that i found that at least tries to make this easier was Sourcetrail, which is essentially dead now: https://www.sourcetrail.com/

Link won't load for me but seems like it's talking about https://github.com/CoatiSoftware/Sourcetrail.