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.
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.