Bump github/super-linter from 6 to 7 #268
dependabot[bot]Annotations
10 errors and 10 warnings
|
The method parameter name 'S' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode1021.java#L49
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'S' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode1021.java#L63
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'J' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode771.java#L32
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'S' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode771.java#L32
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'J' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode771.java#L46
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'S' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode771.java#L46
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'J' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode771.java#L64
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'S' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode771.java#L64
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'A' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode832.java#L33
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
The method parameter name 'S' doesn't match '[a-z][a-zA-Z0-9]*':
src/main/java/com/acesoft/leetcode/LeetCode844.java#L42
Configurable naming conventions for formal parameters of methods and lambdas.
This rule reports formal parameters which do not match the regex that applies to their
specific kind (e.g. lambda parameter, or final formal parameter). Each regex can be
configured through properties.
By default this rule uses the standard Java naming convention (Camel case).
FormalParameterNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_codestyle.html#formalparameternamingconventions
|
|
Use one line for each declaration, it enhances code readability.:
src/main/java/com/acesoft/leetcode/LeetCode1.java#L41
Java allows the use of several variables declaration of the same type on one line.
However, it can lead to quite messy code. This rule looks for several declarations on the same line.
OneDeclarationPerLine (Priority: 4, Ruleset: Best Practices)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_bestpractices.html#onedeclarationperline
|
|
Use one line for each declaration, it enhances code readability.:
src/main/java/com/acesoft/leetcode/LeetCode1.java#L66
Java allows the use of several variables declaration of the same type on one line.
However, it can lead to quite messy code. This rule looks for several declarations on the same line.
OneDeclarationPerLine (Priority: 4, Ruleset: Best Practices)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_bestpractices.html#onedeclarationperline
|
|
Avoid assignments in operands:
src/main/java/com/acesoft/leetcode/LeetCode1021.java#L53
Avoid assignments in operands; this can make code more complicated and harder to read.
AssignmentInOperand (Priority: 3, Ruleset: Error Prone)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_errorprone.html#assignmentinoperand
|
|
Avoid assignments in operands:
src/main/java/com/acesoft/leetcode/LeetCode1021.java#L55
Avoid assignments in operands; this can make code more complicated and harder to read.
AssignmentInOperand (Priority: 3, Ruleset: Error Prone)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_errorprone.html#assignmentinoperand
|
|
Avoid using implementation types like 'Stack'; use the interface instead:
src/main/java/com/acesoft/leetcode/LeetCode1021.java#L64
Excessive coupling to implementation types (e.g., `HashSet`) limits your ability to use alternate
implementations in the future as requirements change. Whenever available, declare variables
and parameters using a more general type (e.g, `Set`).
This rule reports uses of concrete collection types. User-defined types that should be treated
the same as interfaces can be configured with the property `allowedTypes`.
LooseCoupling (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_bestpractices.html#loosecoupling
|
|
Use one line for each declaration, it enhances code readability.:
src/main/java/com/acesoft/leetcode/LeetCode121.java#L36
Java allows the use of several variables declaration of the same type on one line.
However, it can lead to quite messy code. This rule looks for several declarations on the same line.
OneDeclarationPerLine (Priority: 4, Ruleset: Best Practices)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_bestpractices.html#onedeclarationperline
|
|
Use one line for each declaration, it enhances code readability.:
src/main/java/com/acesoft/leetcode/LeetCode125.java#L35
Java allows the use of several variables declaration of the same type on one line.
However, it can lead to quite messy code. This rule looks for several declarations on the same line.
OneDeclarationPerLine (Priority: 4, Ruleset: Best Practices)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_bestpractices.html#onedeclarationperline
|
|
Use one line for each declaration, it enhances code readability.:
src/main/java/com/acesoft/leetcode/LeetCode125.java#L36
Java allows the use of several variables declaration of the same type on one line.
However, it can lead to quite messy code. This rule looks for several declarations on the same line.
OneDeclarationPerLine (Priority: 4, Ruleset: Best Practices)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_bestpractices.html#onedeclarationperline
|
|
Use one line for each declaration, it enhances code readability.:
src/main/java/com/acesoft/leetcode/LeetCode1267.java#L41
Java allows the use of several variables declaration of the same type on one line.
However, it can lead to quite messy code. This rule looks for several declarations on the same line.
OneDeclarationPerLine (Priority: 4, Ruleset: Best Practices)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_bestpractices.html#onedeclarationperline
|
|
Use one line for each declaration, it enhances code readability.:
src/main/java/com/acesoft/leetcode/LeetCode1281.java#L31
Java allows the use of several variables declaration of the same type on one line.
However, it can lead to quite messy code. This rule looks for several declarations on the same line.
OneDeclarationPerLine (Priority: 4, Ruleset: Best Practices)
https://docs.pmd-code.org/pmd-doc-7.5.0/pmd_rules_java_bestpractices.html#onedeclarationperline
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
PMD Report
|
5.61 KB |
|