Affects PMD Version: 6.27
Description:
Since new salesforce release (Winter 21, api version 50) has gone GA over weekend, we've started using new features in our Apex codebase, in particular safe navigation operator (e.g. myObject?.propA?.propB). But unfortunately it looks like pmd just skips all apex classes where safe navigation operator is used - it seems like pmd cannot yet parse this new apex syntax and just silently fails, which results in skipping such troubling apex classes.
Exception Stacktrace:
No error, no stack trace - classes are just skipped from scanning, i.e. no errors are reported from those classes, even when we add deliberately some errors there. But when we remove safe navigation operator from class, it starts reporting errors as before.
Salesforce Release Notes: https://releasenotes.docs.salesforce.com/en-us/winter21/release-notes/rn_apex.htm
Affects PMD Version: 6.27
Description:
Since new salesforce release (Winter 21, api version 50) has gone GA over weekend, we've started using new features in our Apex codebase, in particular safe navigation operator (e.g. myObject?.propA?.propB). But unfortunately it looks like pmd just skips all apex classes where safe navigation operator is used - it seems like pmd cannot yet parse this new apex syntax and just silently fails, which results in skipping such troubling apex classes.
Exception Stacktrace:
No error, no stack trace - classes are just skipped from scanning, i.e. no errors are reported from those classes, even when we add deliberately some errors there. But when we remove safe navigation operator from class, it starts reporting errors as before.
Salesforce Release Notes: https://releasenotes.docs.salesforce.com/en-us/winter21/release-notes/rn_apex.htm