v2 bugsnag #170
Draft
v2 bugsnag #170
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
lavoiesl
force-pushed
the
seb-bugsnag
branch
2 times, most recently
from
17f9706
to
c9e7cd2
Compare
- Remove the logrusbugsnag package in favour of the dedicated Shopify/logrus-bugsnag package - Change the paradigm of adding bugsnag hooks to augment the metadata instead of wrapping calls. - Remove the panic handler by default, since it often causes issues. It is still available as an option.
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.
Significant refactor of the
bugsnagpackage.Design principles / Motivation
Change the paradigm of adding bugsnag hooks to augment the metadata instead of wrapping calls.
This allows more flexibility into which hooks the user may want.
New features
GlobalHookto temporarily capture eventsBreaking changes
Minor changes
Unwrapto thewithClasserror