Add BugsnagErrorTypes for controlling captured errors #561
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
fractalwrench
force-pushed
the
v6-error-types
branch
from
b2bdd20 to
507248b
Compare
fractalwrench
force-pushed
the
v6-error-types
branch
from
507248b to
ae5a7c4
Compare
fractalwrench
force-pushed
the
v6-error-types
branch
from
ae5a7c4 to
c3065a7
Compare
tomlongridge
requested changes
Apr 23, 2020
tomlongridge
approved these changes
Apr 23, 2020
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.
Goal
Adds the
BugsnagErrorTypesclass which controls which errors are captured by Bugsnag. By default, all error types are captured. This replaces the bitmask which was used in the previous implementation.Changeset
BugsnagErrorTypesclassTests
Updated existing test coverage to use new syntax.