Test PR pipline #20
akohan91PMD_validation.yaml
on: pull_request
deploy_verification
/
pmd-analysis
15s
Annotations
10 errors, 10 warnings, and 1 notice
|
The class name 'libak_SuccessResponse' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_SuccessResponse.cls#L5
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The abstract class name 'libak_RestRouter' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_RestRouter.cls#L6
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The class name 'libak_RestProcessor' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_RestProcessor.cls#L6
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The class name 'libak_RestFramework' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_RestFramework.cls#L6
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The class name 'libak_JsonResponse' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_JsonResponse.cls#L5
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The interface name 'libak_IRestResponse' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_IRestResponse.cls#L4
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The interface name 'libak_IRestLogger' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_IRestLogger.cls#L4
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The interface name 'libak_IErrorResponseFactory' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_IErrorResponseFactory.cls#L4
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The class name 'libak_ErrorResponseFactory' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_ErrorResponseFactory.cls#L5
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
The class name 'libak_ErrorResponse' doesn't match '[A-Z][a-zA-Z0-9_]*':
force-app/main/default/classes/libak_ErrorResponse.cls#L5
Configurable naming conventions for type declarations. This rule reports
type declarations which do not match the regex that applies to their
specific kind (e.g. enum or interface). Each regex can be configured through
properties.
By default this rule uses the standard Apex naming convention (Pascal case).
ClassNamingConventions (Priority: 1, Ruleset: Code Style)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_codestyle.html#classnamingconventions
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestRestFramework.cls#L28
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestRestFramework.cls#L8
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestJsonResponse.cls#L141
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestJsonResponse.cls#L108
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestJsonResponse.cls#L75
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestJsonResponse.cls#L42
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestJsonResponse.cls#L9
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestErrorResponseFactory.cls#L38
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestErrorResponseFactory.cls#L4
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Apex unit test classes should have at least one System.runAs() call:
force-app/main/default/classes/tests/libak_TestErrorResponse.cls#L5
Apex unit tests should include at least one runAs method. This makes the tests more robust, and independent from the
user running it.
ApexUnitTestClassShouldHaveRunAs (Priority: 3, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#apexunittestclassshouldhaverunas
|
|
Variable 'processor' defined but not used:
force-app/main/default/classes/tests/libak_TestRestRouter.cls#L53
Detects when a local variable is declared and/or assigned but not used.
UnusedLocalVariable (Priority: 5, Ruleset: Best Practices)
https://docs.pmd-code.org/snapshot/pmd_rules_apex_bestpractices.html#unusedlocalvariable
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
PMD Report
Expired
|
2.36 KB |
sha256:0f40e3752b6384b627c8134e0827a0a13e32210cddbe0e04d847b44dd2c252aa
|
|