New PMD Rules

Updated 1 week ago by Copado Solutions

Copado now supports PMD version 6.38. As part of this upgrade, new rules have been added to the default RuleSet:

  •  The new Apex rule AvoidDebugStatements finds usages of System.debug calls. Debug statements contribute to longer transactions and consume Apex CPU time even when debug logs are not being captured.
  • The new Apex rule InaccessibleAuraEnabledGetter checks that an AuraEnabled getter is public or global. This is necessary if it is referenced in Lightning components.

In order to ensure the rules are updated, follow the steps below.

To add the new rule:

  1. Navigate to Setup > Object Manager > Static Code Analysis Rule.
  2. Go to Fields & Relationships and click on Rule Name.
  3. Scroll down to Values and click on New to add the new rule.
  4. Add the new rule name as a picklist value (note that this name is case sensitive).
  5. Once you have added the new picklist value, go to the Static Code Analysis Setting record and create static code analysis rules for the new value added:
    1. Go to the Static Code Analysis Settings record.
    2. Navigate to the Static Code Analysis Rules related list and click on New to create a new rule:
    3. Select the name of the rule you have added in the Rule Name field.
    4. Add a priority. You can use the one defined by PMD in their documentation or define a custom priority that suits you better.
    5. Enter a message.
    6. Click on Save.

New and Deprecated Rules From Previous PMD Versions 

Version

Rules

6.30

  • New rule: OperationWithLimitsInLoop.
  • Deprecated rules: AvoidDmlStatementsInLoops, AvoidSoqlInLoops and AvoidSoslInLoops.

6.31

  • New rules: OverrideBothEqualsAndHashcode and VfHtmlStyleTagXss.


How did we do?