Fix short circuiting of boolean expressions #7060
Merged
Conversation
This file contains hidden or 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
Boolean expressions with AND (&&) or OR (||) should short circuit as expected for any languages. It helps to support correctly expressions like `isDefined(@exception) && contains(@exception.detailMessage, 'closed')` We are just delegating to the operator evaluation the evaluation of the left and right instead of evaluating operands before the operator.
jpbempel
added
type: bug
evanchooly
approved these changes
May 22, 2024
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.
What Does This Do
We are just delegating to the operator evaluation the evaluation of the left and right instead of evaluating operands before the operator.
Motivation
Boolean expressions with AND (&&) or OR (||) should short circuit as expected for any languages. It helps to support correctly expressions like
isDefined(@exception) && contains(@exception.detailMessage, 'closed')Additional Notes
Jira ticket: DEBUG-2232