Showing 67 of 67 total issues
The method 'getInit' has a Standard Cyclomatic Complexity of 16. Open
public void getInit() {
- Read upRead up
- Exclude checks
StdCyclomaticComplexity
Since: PMD 5.5.0
Priority: Medium
Categories: Complexity
Remediation Points: 12500000
Complexity directly affects maintenance costs is determined by the number of decision points in a method plus one for the method entry. The decision points include 'if', 'while', 'for', and 'case labels' calls. Generally, numbers ranging from 1-4 denote low complexity, 5-7 denote moderate complexity, 8-10 denote high complexity, and 11+ is very high complexity.
Example:
// This has a Cyclomatic Complexity = 12
public class Foo {
1 public void example() {
2 if (a == b || (c == d && e == f)) {
3 if (a1 == b1) {
fiddle();
4 } else if a2 == b2) {
fiddle();
} else {
fiddle();
}
5 } else if (c == d) {
6 while (c == d) {
fiddle();
}
7 } else if (e == f) {
8 for (int n = 0; n < h; n++) {
fiddle();
}
} else {
switch (z) {
9 case 1:
fiddle();
break;
10 case 2:
fiddle();
break;
11 case 3:
fiddle();
break;
12 default:
fiddle();
break;
}
}
}
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
showMethodsComplexity | true | Add method average violations to the report |
showClassesComplexity | true | Add class average violations to the report |
cc_categories | Complexity | Code Climate Categories |
ccremediationpoints_multiplier | 250 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
reportLevel | 10 | Cyclomatic Complexity reporting threshold |
The class 'TableGridController' has a Standard Cyclomatic Complexity of 2 (Highest = 16). Open
public with sharing class TableGridController {
- Read upRead up
- Exclude checks
StdCyclomaticComplexity
Since: PMD 5.5.0
Priority: Medium
Categories: Complexity
Remediation Points: 12500000
Complexity directly affects maintenance costs is determined by the number of decision points in a method plus one for the method entry. The decision points include 'if', 'while', 'for', and 'case labels' calls. Generally, numbers ranging from 1-4 denote low complexity, 5-7 denote moderate complexity, 8-10 denote high complexity, and 11+ is very high complexity.
Example:
// This has a Cyclomatic Complexity = 12
public class Foo {
1 public void example() {
2 if (a == b || (c == d && e == f)) {
3 if (a1 == b1) {
fiddle();
4 } else if a2 == b2) {
fiddle();
} else {
fiddle();
}
5 } else if (c == d) {
6 while (c == d) {
fiddle();
}
7 } else if (e == f) {
8 for (int n = 0; n < h; n++) {
fiddle();
}
} else {
switch (z) {
9 case 1:
fiddle();
break;
10 case 2:
fiddle();
break;
11 case 3:
fiddle();
break;
12 default:
fiddle();
break;
}
}
}
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
showMethodsComplexity | true | Add method average violations to the report |
showClassesComplexity | true | Add class average violations to the report |
cc_categories | Complexity | Code Climate Categories |
ccremediationpoints_multiplier | 250 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
reportLevel | 10 | Cyclomatic Complexity reporting threshold |
Too many fields Open
public with sharing class TableGridController {
- Read upRead up
- Exclude checks
TooManyFields
Since: PMD 5.5.0
Priority: Medium
Categories: Complexity
Remediation Points: 10000000
Classes that have too many fields can become unwieldy and could be redesigned to have fewer fields, possibly through grouping related fields in new objects. For example, a class with individual city/state/zip fields could park them within a single Address field.
Example:
public class Person {
// too many separate fields
int birthYear;
int birthMonth;
int birthDate;
float height;
float weight;
}
public class Person {
// this is more manageable
Date birthDate;
BodyMeasurements measurements;
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
cc_categories | Complexity | Code Climate Categories |
ccremediationpoints_multiplier | 200 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
maxfields | 20 | Max allowable fields |
This class has too many public methods and attributes Open
public with sharing class TableGridController {
- Read upRead up
- Exclude checks
ExcessivePublicCount
Since: PMD 5.5.0
Priority: Medium
Categories: Complexity
Remediation Points: 7500000
Classes with large numbers of public methods and attributes require disproportionate testing efforts since combinational side effects grow rapidly and increase risk. Refactoring these classes into smaller ones not only increases testability and reliability but also allows new variations to be developed easily.
Example:
public class Foo {
public String value;
public Bar something;
public Variable var;
// [... more more public attributes ...]
public void doWork() {}
public void doMoreWork() {}
public void doWorkAgain() {}
// [... more more public methods ...]
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
topscore | Top score value | |
minimum | 25.0 | Minimum reporting threshold |
cc_categories | Complexity | Code Climate Categories |
ccremediationpoints_multiplier | 150 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
sigma | Sigma value |
Apex classes should escape variables merged in DML query Open
Database.query(tmpSoql);
- Read upRead up
- Exclude checks
ApexSOQLInjection
Since: PMD 5.5.3
Priority: Medium
Categories: Security
Remediation Points: 5000000
Detects the usage of untrusted / unescaped variables in DML queries.
Example:
public class Foo {
public void test1(String t1) {
Database.query('SELECT Id FROM Account' + t1);
}
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
cc_categories | Security | Code Climate Categories |
ccremediationpoints_multiplier | 100 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
Avoid long parameter lists Open
public static void putFromString(SObject theObject, String field, Schema.DisplayType fieldType, String value) {
- Read upRead up
- Exclude checks
ExcessiveParameterList
Since: PMD 5.5.0
Priority: Medium
Categories: Complexity
Remediation Points: 2500000
Methods with numerous parameters are a challenge to maintain, especially if most of them share the same datatype. These situations usually denote the need for new objects to wrap the numerous parameters.
Example:
// too many arguments liable to be mixed up
public void addPerson(int birthYear, int birthMonth, int birthDate, int height, int weight, int ssn) {
...
}
// preferred approach
public void addPerson(Date birthdate, BodyMeasurements measurements, int ssn) {
...
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
topscore | Top score value | |
minimum | 4.0 | Minimum reporting threshold |
cc_categories | Complexity | Code Climate Categories |
ccremediationpoints_multiplier | 50 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
sigma | Sigma value |
Avoid long parameter lists Open
public FilterStatement(String sobjectName, String fieldName, String operator, String valueAsString) {
- Read upRead up
- Exclude checks
ExcessiveParameterList
Since: PMD 5.5.0
Priority: Medium
Categories: Complexity
Remediation Points: 2500000
Methods with numerous parameters are a challenge to maintain, especially if most of them share the same datatype. These situations usually denote the need for new objects to wrap the numerous parameters.
Example:
// too many arguments liable to be mixed up
public void addPerson(int birthYear, int birthMonth, int birthDate, int height, int weight, int ssn) {
...
}
// preferred approach
public void addPerson(Date birthdate, BodyMeasurements measurements, int ssn) {
...
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
topscore | Top score value | |
minimum | 4.0 | Minimum reporting threshold |
cc_categories | Complexity | Code Climate Categories |
ccremediationpoints_multiplier | 50 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
sigma | Sigma value |
Apex classes should declare a sharing model if DML or SOQL is used Open
public class TableGridTestHelper {
- Read upRead up
- Exclude checks
ApexSharingViolations
Since: PMD 5.5.3
Priority: Medium
Categories: Security
Remediation Points: 1000000
Detect classes declared without explicit sharing mode if DML methods are used. This forces the developer to take access restrictions into account before modifying objects.
Example:
public class without sharing Foo {
// DML operation here
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
cc_categories | Security | Code Climate Categories |
ccremediationpoints_multiplier | 20 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
Variables should start with a lowercase character, 'ALL_TYPES' starts with uppercase character. Open
List<Schema.DisplayType> ALL_TYPES = new List<Schema.DisplayType>();
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Only variables that are final should contain underscores (except for underscores in standard prefix/suffix), 'OBJECT_DESCRIBES' is not final. Open
private static Map<String, Schema.DescribesObjectResult> OBJECT_DESCRIBES;
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Variables should start with a lowercase character, 'FIELDS' starts with uppercase character. Open
private static Map<String, Map<String, Schema.SObjectField>> FIELDS;
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Variables that are final and static should be all capitals, 'Label' is not all capitals. Open
Label, Value
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Variables should start with a lowercase character, 'OBJECT_DESCRIBES' starts with uppercase character. Open
private static Map<String, Schema.DescribesObjectResult> OBJECT_DESCRIBES;
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Variables that are final and static should be all capitals, 'validTypesFor' is not all capitals. Open
private static final Map<String, List<Schema.DisplayType>> validTypesFor;
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Variables should start with a lowercase character, 'FIELD_DESCRIBES' starts with uppercase character. Open
private static Map<String, Map<String, Schema.DescribeFieldResult>> FIELD_DESCRIBES;
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Variables that are final and static should be all capitals, 'integerField' is not all capitals. Open
final static Schema.SObjectField integerField = TableGridTestHelper.integerField();
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Only variables that are final should contain underscores (except for underscores in standard prefix/suffix), 'ALL_TYPES' is not final. Open
List<Schema.DisplayType> ALL_TYPES = new List<Schema.DisplayType>();
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Variables that are final and static should be all capitals, 'stringField' is not all capitals. Open
final static Schema.SObjectField stringField = TableGridTestHelper.textField();
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Only variables that are final should contain underscores (except for underscores in standard prefix/suffix), 'FIELD_DESCRIBES' is not final. Open
private static Map<String, Map<String, Schema.DescribeFieldResult>> FIELD_DESCRIBES;
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |
Variables that are final and static should be all capitals, 'Value' is not all capitals. Open
Label, Value
- Read upRead up
- Exclude checks
VariableNamingConventions
Since: PMD 5.5.0
Priority: Medium
Categories: Style
Remediation Points: 250000
A variable naming conventions rule - customize this to your liking. Currently, it checks for final variables that should be fully capitalized and non-final variables that should not include underscores.
Example:
public class Foo {
public static final Integer MY_NUM = 0;
public String myTest = '';
DataModule dmTest = new DataModule();
}
PMD properties
Name | Value | Description |
---|---|---|
violationSuppressRegex | Suppress violations with messages matching a regular expression | |
violationSuppressXPath | Suppress violations on nodes which match a given relative XPath expression. | |
parameterSuffix | Method parameter variable suffixes | |
parameterPrefix | Method parameter variable prefixes | |
localSuffix | Local variable suffixes | |
localPrefix | Local variable prefixes | |
memberSuffix | Member variable suffixes | |
memberPrefix | Member variable prefixes | |
staticSuffix | Static variable suffixes | |
staticPrefix | Static variable prefixes | |
checkParameters | true | Check constructor and method parameter variables |
checkLocals | true | Check local variables |
cc_categories | Style | Code Climate Categories |
ccremediationpoints_multiplier | 5 | Code Climate Remediation Points multiplier |
ccblockhighlighting | false | Code Climate Block Highlighting |
checkMembers | true | Check member variables |