Repository navigation
[13.x] Fix using elsePushIf blade directive with complex conditions - #61741
Merged
taylorotwell merged 1 commit intoSep 26, 2026
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
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 pr fixes
@elsePushIfdirective when condition have multiple commas.this problem was already fixed for
@pushIfin #57274 (related issue: #57264), since that fix is already merged and confirmed, but the original pr missed fixing@elsePushIf, so i implemented the same fix for it here.Cause:
compileElsePushIf()usesexplode(',', ..., 2), which splits at the first comma.Before
To:
❌ compiled incorrectly: the condition get split at it's first comma, which is a PHP parse error.
After
✅ compiles correctly:
To: