-
Notifications
You must be signed in to change notification settings - Fork 27
Closed
Labels
bugSomething isn't workingSomething isn't working
Milestone
Description
It seems, that issue #51 reappeared...
Log output:
src\classes2\AllInOne.cls:2:FieldNamingConventions (Priority: 1):The instance field name 'INSTANCE_FIELD' doesn't match '[a-z][a-zA-Z0-9]*'
Error: Configurable naming conventions for field declarations. This rule reports variable declarations
which do not match the regex that applies to their specific kind ---e.g. constants (static final),
static field, final field. Each regex can be configured through properties.
By default this rule uses the standard Apex naming convention (Camel case).
FieldNamingConventions (Priority: 1, Ruleset: Code Style)
https://pmd.github.io/pmd-6.55.0/pmd_rules_apex_codestyle.html#fieldnamingconventions
That means, we use backslashes as path separators. That means, in the sarif.json file, there are no valid URIs anymore...
{
"ruleId": "FieldNamingConventions",
"ruleIndex": 0,
"message": {
"text": "The instance field name 'INSTANCE_FIELD' doesn't match '[a-z][a-zA-Z0-9]*'"
},
"locations": [
{
"physicalLocation": {
"artifactLocation": {
"uri": "src\\classes2\\AllInOne.cls"
},
"region": {
"startLine": 2,
"startColumn": 13,
"endLine": 2,
"endColumn": 26
}
}
}
]
},I think, these should be forward slashes....
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working