112 missing validations on if, while & do-while #230
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.
This added checking the expressions on these statements return Boolean values. For once that rule appears to be universal and there are no assignability concerns.
As part of this I have simplified the way we add Issues a little so you don't need to provide the path separately from the range. I think this previously used to be an issue due to the apexlink/pkgforce split if I am recalling correctly. Have have also included some minor IntelliJ warning fixes that got flagged due to the Issue change.
There is a bug the apex-parser on do-while in that it allows single statements but Apex only supports blocks, just to make it different from if & while. I will create a seperate tickets for correcting this.