[12.x] Display closures and standalone functions correctly in exception trace#58879
Merged
taylorotwell merged 2 commits intoFeb 17, 2026
Merged
Conversation
avosalmon
commented
Feb 17, 2026
Comment on lines
+123
to
+128
| if (count($trace) > 1 && empty($trace[0]['class']) && empty($trace[0]['function'])) { | ||
| $trace[0]['class'] = $trace[1]['class'] ?? ''; | ||
| $trace[0]['type'] = $trace[1]['type'] ?? ''; | ||
| $trace[0]['function'] = $trace[1]['function'] ?? ''; | ||
| $trace[0]['args'] = $trace[1]['args'] ?? []; | ||
| } |
Contributor
Author
There was a problem hiding this comment.
The throw-point frame added by FlattenException (which has file/line but no class/function) is now enriched with the executing function's data from the next trace entry, so closures like UserController->{closure:UserController::show():19}() display correctly.
taylorotwell
deleted the
exception-renderer-standalone-function-display
branch
DarkGhostHunter
pushed a commit
to DarkGhostHunter/laravel-framework
that referenced
this pull request
Feb 22, 2026
…on trace (laravel#58879) * Display closures and standalone functions correctly in exception trace * Fix test
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
2 participants
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.
The exception renderer's trace frames now use each frame's own trace data (
class,type,function) instead of stitching together the classmap class with the previous frame's callable. This fixes two issues:array_mapwere concatenated directly onto the class name (e.g.UserControllerarray_map()) due to the missing operatorBefore
After