PMD Rules
- PMD – Apex Class Rules
- PMD – Apex Trigger Rules
- PMD – Lightning Rules
- Accessing Endpoints Over Unencrypted Http Should Be Avoided
- Access Permissions Should Be Checked Before A SOQL/SOSL/DML Operation
- Apex Unit Tests Should Include At Least One Assertion
- Apex Unit Tests Should Not Use @isTest(seeAllData=true)
- Avoid Classes With Too Many Fields
- Avoid Classes With Too Many Public Methods
- Avoid Constructors With Excessive Lines of Code Count
- Avoid Creating Deeply Nested If-Then Statements
- Avoid Declaring Multiple Variables In A Single Line
- Avoid DML Statements Inside Loops
- Avoid Empty Block Statements
- Avoid Empty Catch Block
- Avoid Empty If Statements
- Avoid Empty Try Or Finally Blocks
- Avoid Empty While Statements
- Avoid Excessive Class File Lengths
- Avoid Excessive Cyclomatic Complexity
- Avoid Excessive Standard Cyclomatic Complexity
- Avoid Hardcoded Credentials Used In Requests To An Endpoint
- Avoid Hardcoding IDs
- Avoid Implementing Business Logic In Triggers
- Avoid Methods With Excessive Lines Of Code Count
- Avoid Processing Unescaped URL Parameters
- Avoid SOQL Inside Loops
- Avoid Sosl Calls Within Loops
- Avoid System.debug And Configuration.disableTriggerCRUDSecurity()
- Avoid Types With Excessive Lines Of Code Count
- Avoid Using “for” Statements Without Using Surrounding Braces
- Avoid Using “while” Statements Without Using Braces To Surround The Code Block
- Avoid Using DML Operations In Apex Class Constructor/Init Method
- Avoid Using If…Else Statements Without Using Surrounding Braces
- Avoid Using If Statements Without Using Braces To Surround The Code Block
- Avoid Using Untrusted / Unescaped Variables In DML Queries
- Calls To addError With Disabled Escaping Should Be Avoided
- Classes Should Explicitly Declare A Sharing Mode If DML Methods Are Used
- Class Names Should Always Begin With An Upper Case Character
- Final Variables Should Be Fully Capitalized And Non-Final Variables Should Not Include Underscores
- Method Names Should Always Begin With A Lower Case Character And Should Not Contain Underscores
- Methods With Numerous Parameters Should Not Be Used
- Missing ApexDoc @description
- Missing ApexDoc Comment
- Non-Constructor Methods Should Not Have The Same Name As The Enclosing Class
- Randomly Generated IVs And Keys Should Be Used For Crypto Calls
- Redirects To User-Controlled Locations Should Be Avoided
- The Global Modifier Should Be Avoided
- Variable Names Should Start With A Lowercase Character
- Variables Should Start With A Lowercase Character
- Avoid Directly Accessing Trigger.old And Trigger.new
- Avoid Using The With Keyword
- Avoid Functions With Inconsistent Return Types
- Avoid Unintended Global Variables
- Avoid Unintended Modification Of Variables Outside Loops
- Avoid Using The ParseInt Function Without An Explicit Base Parameter
- Avoid Assignments In Operands
- Avoid Using For Statements Without Using Curly Braces
- Avoid Using If…Else Statements Without Using Curly Braces
- Avoid Using If Statements Without Using Curly Braces
- Avoid Return Statements In If Blocks
- Avoid Unnecessary Code Blocks
- Avoid Unnecessary Parenthesis
- Avoid Using “while” Statements Without Using Curly Braces
- Avoid Trailing Commas In Object Or Array Literals
- Avoid Use Of The “==” Operator
- Avoid Declaring Integers Over 15 Digits
- All Apex Classes Should Have At Least One Test Class
- “System.debug” First Parameter Has To Be Logging Level
- Apex Assertions Should Include Message
- Apex Unit Test Method Should Have “@IsTest” Annotation
- Field Naming Conventions
- Formal Parameter Naming Conventions
- Local Variable Naming Conventions
- Method Naming Conventions
- Property Naming Conventions
- Cognitive Complexity
- Avoid Non Existent Annotations
- Inaccessible Aura Enabled Getter
- Override Both Equals And Hashcode
- Eagerly Loaded Describe SObject Result
- Test Methods Must Be In Test Classes
- Field Declarations Should Be At Start
- Unused Local Variable
- Avoid Non Restrictive Queries
- Avoid Queueable Without Finalizer
- Avoid Operation With High Cost In Loop
- Remove unused public methods
- Remove unused private methods
- Remove unused apex classes