Skip to content
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

Merged
merged 4 commits into from
Feb 3, 2016

Conversation

kattrali
Copy link
Contributor

@kattrali kattrali commented Feb 2, 2016

Changes

  • Set and serialize default severity as error in case of an uncaught exception. It is still overridden in the case of a handled exception.
  • Serialize breadcrumbs after each change
  • Refactor serializedDictionary:toJSON: into a function, BSSerializeJSONDictionary
  • Rename onCrash handler to indicate purpose

Fixes #58

[self resetDefaultSeverity];
}

- (void) resetDefaultSeverity {
Copy link
Contributor

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?

Copy link
Contributor Author

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?

Copy link
Contributor

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.

Copy link
Contributor Author

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.

@snmaynard
Copy link
Contributor

This LGTM!

Use error as the default severity, which is overridden by manual error
notifications
@kattrali kattrali force-pushed the kattrali/send-severity-breadcrumbs-with-uncaught branch from f05c0af to a94ddb4 Compare February 3, 2016 19:36
@snmaynard
Copy link
Contributor

👍 👍 🌳

kattrali added a commit that referenced this pull request Feb 3, 2016
…s-with-uncaught

Send severity and breadcrumbs with uncaught exceptions
@kattrali kattrali merged commit d60b6ec into master Feb 3, 2016
@kattrali kattrali deleted the kattrali/send-severity-breadcrumbs-with-uncaught branch February 3, 2016 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants