Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[DevTools] Print component stacks as error objects to get source mapping #30289

Merged
merged 2 commits into from
Jul 8, 2024
Merged

[DevTools] Print component stacks as error objects to get source mapping #30289

merged 2 commits into from
Jul 8, 2024

Commits on Jul 8, 2024

  1. Print component stacks as error objects to get source mapping

    @sebmarkbage
    sebmarkbage committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    5c7871b View commit details
    Browse the repository at this point in the history

  2. Don't try to format if the log already had a component stack in stric… 

    …t mode override

We've already merged the stack with the message at this point so would need further refactoring to handle.

This is non-essential and often just fully hidden.
    @sebmarkbage
    sebmarkbage committed Jul 8, 2024
    Configuration menu
    Copy the full SHA
    5b3ebf0 View commit details
    Browse the repository at this point in the history