Improve validation on Expression Statement #234
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pwrightcertinia
approved these changes
Sep 25, 2023
kjonescertinia
deleted the
118-missing-handling-expression-can-not-be-a-statement-error
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 add validation to ExpressionStatement (expression used as a statement) to handle the equivalent of the "Expression cannot be a statement" error you get in Apex.
There are actually very few expressions that can be used as statements, broadly they are method & constructor call expressions, assignment expressions, new expression. You can also put brackets around these which is a sub expression in our CST.