David Schach
My feedback
14 results found
-
1 vote1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment -
1 vote
Hi!
Our static code analysis is built on PMD. Currently, the only error suppression that works with Apex code in PMD is the `@SuppressWarnings` annotation. (This was introduced for Apex in PMD version 6.0.0). As you say, you can suppress all rules, or specific rules, at the class level, but can’t make more fine grained suppressions, unfortunately.
There are other methods of suppressing errors within PMD for other languages, but these don’t currently work with Apex. We’ll keep an eye on future versions of PMD to see if they introduce new methods of suppressing warnings for Apex code.
An error occurred while saving the comment PMD can now suppress warnings at a more granular level in a class.
1. Use //NOPMD on a line
2. Use @SuppressWarnings('PMD.AvoidGlobalModifier') for example above the class declaration line
3. @SuppressWarnings('PMD.FieldNamingConventions') above an inner class
etc
You basically find the PMD class API name and add that to whatever classes or methods you'd like.
https://pmd.github.io/latest/pmd_userdocs_suppressing_warnings.html (note the specific formatting for Apex) -
4 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
4 votes
-
11 votes
-
3 votes
-
4 votes
-
12 votes
-
4 votes
-
10 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
14 votes
-
2 votes
-
4 votes
-
9 votes
Following up: Many users put all test classes into a separate folder force-app/main/default/tests and SFDX still recognizes them as Apex for that project. New classes are still saved to the default folder, but can be moved.
Please find Apex wherever it is and include it in the comparison.