Allow extensions to send stack trace on error - #1980
Open
JosephVolosin wants to merge 1 commit into
Open
Conversation
JosephVolosin
temporarily deployed
to
test-workflow
August 5, 2026 16:13 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
|
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
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.
This PR slightly modifies the
ExtensionResponseobject to allow for an optionaltrace?: string. This is so extensions can optionally send back their own stack trace with the error to help debugging. By tagging this onto thethrow new Errorvia. theErrorOptions, the stack trace is printed out in the expanded log message, while keeping the message itself shorter.