Fix: handle ParseError in hasEvenNumberOfParentheses when Xdebug triggers malformed expression #57541
+13
−6
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
…gers malformed expression
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
When Xdebug is enabled,
token_get_all()may throw aParseErrorfor incomplete or malformed Blade expressions.This causes tests or runtime Blade compilation to crash with:
Fix
Added a
try/catch (\ParseError)block aroundtoken_get_all()inIlluminate\View\Compilers\BladeCompiler::hasEvenNumberOfParentheses.If a parse error occurs, the method now gracefully returns
falseinstead of crashing.Impact
Prevents test suite and runtime crashes under Xdebug
Keeps behavior identical for valid expressions
No breaking changes, PSR-12 and Pint-compliant
Related issue
Fixes #57472