[apex] New Rule: Avoid boolean method parameters #5821
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the PR
This PR implements a new Apex rule
AvoidBooleanMethodParametersRulethat detects boolean parameters in public and global methods. The rule discourages the use of Boolean parameters in public APIs as they can lead to ambiguity (especially with null handling in Apex) and make method calls harder to understand. Instead, the rule encourages developers to use more expressive alternatives such as separate methods with descriptive names, enums, or configuration objects.The rule specifically targets:
Related issues
Ready?
./mvnw clean verifypasses (checked automatically by github actions)