fix(expressions): return actual values from and/or operators instead of booleans #362
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.



Fixes #276
The
andandoroperators were returning boolean values instead of the actual evaluated values. This broke patterns like{% if "x" in (val or "") %}becauseval or ""evaluated toTrueinstead of the actual string value.Now matches Python/Django behavior:
"hello" or "world"returns"hello"(notTrue)"" or "default"returns"default"(notTrue)"hello" and "world"returns"world"(notTrue)