Skip to content

[apex] Fixes for experimental apex parser#4739

Merged
adangel merged 18 commits into
pmd:experimental-apex-parserfrom
adangel:issue-4722-apex-fixes
Jan 12, 2024
Merged

[apex] Fixes for experimental apex parser#4739
adangel merged 18 commits into
pmd:experimental-apex-parserfrom
adangel:issue-4722-apex-fixes

Conversation

@adangel

@adangel adangel commented Nov 5, 2023

Copy link
Copy Markdown
Member

This must not be called in multiple threads as we otherwise stop logging
to System.err.
@ghost

ghost commented Nov 5, 2023

Copy link
Copy Markdown
2 Messages
📖 Compared to experimental-apex-parser:
This changeset changes 9 violations,
introduces 630 new violations, 0 new errors and 0 new configuration errors,
removes 6 violations, 13 errors and 0 configuration errors.
Download full report as build artifact
📖 Compared to master:
This changeset changes 3 violations,
introduces 3 new violations, 0 new errors and 0 new configuration errors,
removes 3 violations, 0 errors and 0 configuration errors.
Download full report as build artifact
Compared to experimental-apex-parser:
This changeset changes 9 violations,
introduces 54 new violations, 0 new errors and 0 new configuration errors,
removes 6 violations, 13 errors and 0 configuration errors.
Download full report as build artifact
Compared to master:
This changeset changes 3 violations,
introduces 3 new violations, 0 new errors and 0 new configuration errors,
removes 3 violations, 0 errors and 0 configuration errors.
Download full report as build artifact
Compared to experimental-apex-parser:
This changeset changes 9 violations,
introduces 195 new violations, 0 new errors and 0 new configuration errors,
removes 67 violations, 15 errors and 0 configuration errors.
Download full report as build artifact
Compared to master:
This changeset changes 3 violations,
introduces 3 new violations, 0 new errors and 0 new configuration errors,
removes 3 violations, 0 errors and 0 configuration errors.
Download full report as build artifact
Compared to experimental-apex-parser:
This changeset changes 9 violations,
introduces 195 new violations, 0 new errors and 0 new configuration errors,
removes 67 violations, 15 errors and 0 configuration errors.
Download full report as build artifact
Compared to master:
This changeset changes 3 violations,
introduces 3 new violations, 0 new errors and 0 new configuration errors,
removes 3 violations, 0 errors and 0 configuration errors.
Download full report as build artifact
Compared to experimental-apex-parser:
This changeset changes 4 violations,
introduces 155 new violations, 1 new errors and 0 new configuration errors,
removes 4 violations, 7 errors and 0 configuration errors.
Download full report as build artifact
Compared to master:
This changeset changes 8 violations,
introduces 66 new violations, 9 new errors and 0 new configuration errors,
removes 43 violations, 0 errors and 0 configuration errors.
Download full report as build artifact
Compared to experimental-apex-parser:
This changeset changes 0 violations,
introduces 176 new violations, 0 new errors and 0 new configuration errors,
removes 0 violations, 13 errors and 0 configuration errors.
Download full report as build artifact
Compared to master:
This changeset changes 12 violations,
introduces 68 new violations, 2 new errors and 0 new configuration errors,
removes 20 violations, 0 errors and 0 configuration errors.
Download full report as build artifact

Generated by 🚫 Danger

For empty catch blocks, there is the separate rule EmptyCatchBlock.
EmptyStatementBlock shouldn't report these.

Refs pmd#4722
now the reported violations are correct: each if block is reported.
With Apex Jorje, the line numbers of the second if block were wrong and
two violations on the same line were
reported.
Using now FieldDeclarations instead of Fields for report location.

Refs pmd#4722
Using now FieldDeclarations instead of Fields for report location.

Refs pmd#4722
Interface methods are implicit public and abstract

Refs pmd#4722
Note: Apex Jorje variant didn't consider comments for fields at all.

Refs pmd#4722
Note: previously, there was no space between type params, now there is.

Refs pmd#4722
This should fix some of the parsing errors.
@adangel adangel marked this pull request as ready for review January 5, 2024 14:45
@adangel adangel merged commit 035909c into pmd:experimental-apex-parser Jan 12, 2024
@adangel adangel deleted the issue-4722-apex-fixes branch January 12, 2024 09:47
@adangel adangel added this to the 7.0.0 milestone Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[apex] New Parser - parsing errors and rule differences

1 participant