refactor: extract Laravel stack trace to dedicated component for better performance #481
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
arukompas
deleted the
refactor/laravel-stack-trace-display-improvements
branch
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.
Summary
Refactored Laravel stack trace visualization into a dedicated component to fix performance issues and improve code organization.
Changes
LaravelStackTraceDisplay.vuewith computed property for single-parse optimizationgetStackTraceData()calls per log entry (~85% reduction)Before/After
Before: Regex parsing executed 7+ times per log (every template interpolation)
After: Stack trace parsed once via Vue computed property
Testing
npm run dev