-
Notifications
You must be signed in to change notification settings - Fork 130
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.
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
Send severity and breadcrumbs with uncaught exceptions #86
Send severity and breadcrumbs with uncaught exceptions #86
Conversation
[self resetDefaultSeverity]; | ||
} | ||
|
||
- (void) resetDefaultSeverity { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we instead say that if severity is nil then we should set it to error in the sink?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wondered about that. Is it weird to modify the payloads during the filter step though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dont think so. I think we'd just be saying that if one wasnt written it was in fact an error. I dont mind which direction we head in but wanted to point it out as an option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I could see that. and then I can move all of this logic as one unit. Patched.
This LGTM! |
Use error as the default severity, which is overridden by manual error notifications
f05c0af
to
a94ddb4
Compare
👍 👍 🌳 |
…s-with-uncaught Send severity and breadcrumbs with uncaught exceptions
Changes
error
in case of an uncaught exception. It is still overridden in the case of a handled exception.serializedDictionary:toJSON:
into a function,BSSerializeJSONDictionary
Fixes #58