feat: allow errors to provide their own stack traces #51
Conversation
This file contains 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
james-lawrence
force-pushed
the
errors-stacktraces
branch
from
324beb6
to
e6d78a2
Compare
this allows errors to report their actual stack trace without requiring honeybadger to be used to generate the error.
james-lawrence
force-pushed
the
errors-stacktraces
branch
from
e6d78a2
to
9ab217d
Compare
stympy
approved these changes
Apr 23, 2024
subzero10
changed the title
|
@james-lawrence This was released with |
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.
Status
READY
Description
this allows errors to report their actual stack trace without requiring honeybadger to be used to generate the error. related #48.
minor note: not my ideal approach due to the lack of standardization in the ecosystem for this but its a starting point.
Todos