You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the class apex.rule.security.Helper provides many utility methods for generating a fully qualified name of variables, fields, methods. They use the format "<defining_type>:".
I'm wondering, whether this actually works here in PMD, if Class A references Class B,
but we let parse the files separately. I guess, the parser then doesn't resolve this?
Expose the "definingType" on the AbstractApexNode: Each jorje node has a reference to its
defining type, which holds information about the compilation unit name.
ApexNode.getNode()package-privateASTLiteralExpression.getLiteralType(), we expose a Jorje-internal Enum. Using this, makes the rule again dependent on jorje. Same withASTBooleanExpression.getOperator(). This has been done by [apex] Remove Jorje leaks outsideastpackage #4081 and [visualforce] Replace uses of Jorje types in pmd-visualforce #4226 on PMD6apex.rule.security.Helperprovides many utility methods for generating a fully qualified name of variables, fields, methods. They use the format "<defining_type>:".I'm wondering, whether this actually works here in PMD, if Class A references Class B,
but we let parse the files separately. I guess, the parser then doesn't resolve this?
defining type, which holds information about the compilation unit name.
CanSuppressWarningsis deprecated.