Skip to content

[BUGFIX] Ignore f:then/f:else outside condition context #1052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

s2b
Copy link
Contributor

@s2b s2b commented Apr 16, 2025

Before this change, both f:then and f:else could be used outside of
a condition tag and would then always output the content, regardless
of any condition. Now, nothing is outputted.

In the future, we might consider throwing an exception here to alert the
user about invalid Fluid syntax. However, this would be a breaking change.

Resolves: #1020

@s2b s2b force-pushed the bugfix/thenElseOutsideIf branch from edabe97 to 0a39cd6 Compare April 16, 2025 22:19
Before this change, both `f:then` and `f:else` could be used outside of
a condition tag and would then always output the content, regardless
of any condition. Now, nothing is outputted.

In the future, we might consider throwing an exception here to alert the
user about invalid Fluid syntax. However, this would be a breaking change.

Resolves: #1020
@s2b s2b force-pushed the bugfix/thenElseOutsideIf branch from 0a39cd6 to 2adbed4 Compare April 17, 2025 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: f:else inside f:else always executed
2 participants