PMD VS ESLint

PMD is a source code static analysis tool. It inspects your Java files for any issues, and has a configurable set of rules to look at.

While the security findings can be pretty elaborate and helpful, the code quality and performance focused findings are not that impressive and can often be detected by more basic or powerful tools like SonarQube (paying) or PMD (free). To see what I mean you can have a look at the list of Java code quality detectors, which is pretty short and contains a lot of simple findings like:

Also saw this convo has a couple years worth of ideas going on … https://github.com/pmd/pmd/issues/3413

PMD and Checkstyle are static analysis tools that check your code on each project build. Gradle allows to apply them easily.

The generated classes should be put into .gitignore. Otherwise, if you have Checkstyle, PMD, or SonarQube in your project, then generated classes can violate some rules. Besides, if you don't put them into .gitignore, then each pull request might become huge due to the fact that even a slightest fix can lead to lots of changes in the generated classes.

- PMD Static Code Analysis tool: https://pmd.github.io/

PMD, Spotbugs, Nullaway: Java linting/static analysis (https://pmd.github.io, https://spotbugs.github.io, https://github.com/uber/NullAway)

PMD, and checkstyle as well.

Open up the config/ruleset.xml file, and you’ll find an XML document that lists several rules. These rules map to the issues which PMD will report on. Believe it or not, there are hundreds of Apex rules, and you can find the full set at the PMD repo. You have complete control over which rules to enable. Typically, you’d determine which ones are important by agreeing with your teammates on the ones that matter most. After all, their code will be statically analyzed, too!

ESLint: Finds JavaScript problems

Link

Use Static Code Analysis Tools: Tools like ESLint can help identify potential code injection points.

To learn more about ESLint, check out the official ESLint documentation. To learn more about Prettier, check out the official Prettier documentation.

Use linting tools to enforce consistent code style and catch potential issues. Prettier can help auto-format to a consistent style, while Eslint can help with more nuanced consistency checks that you can easily customize with your own plugins.

ESLint for code linting

ESLint

In this example, ESLint reported two errors due to violation of the rules no-unused-vars and no-undef: The ESLint GitHub project is organized in a monorepo, and you can consult more configuration options by looking into the @eslint/js package. The above config adds all recommended rules, which all have a severity level of error. We will learn more about violation severity in a minute.

✅ Angular 18 ✅ Angular Material ✅ Unit Testing with Jest ✅ End-to-End Testing with Cypress ✅ Internationalization with Transloco ✅ Auto documentation with Compodoc ✅ Provide component examples with Storybook ✅ Analyse your project with source-map-explorer ✅ Docker ✅ ESLint ✅ Prettier ✅ Commit Linting ✅ AuditJS Audit this application using Sonatype OSS Index ✅ Auto-generate a CHANGELOG with auto-changelog

There is a popular open-source JavaScript linting tool called ESLint, which is used for automatically detecting incorrect patterns found in JavaScript code.