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

Support exception chaining #312

Merged
merged 2 commits into from
Apr 8, 2015

Conversation

javawizard
Copy link
Contributor

Fixes #190

@dcramer
Copy link
Member

dcramer commented Apr 3, 2015

Unrelated to the code, but any idea which version of Ruby started offering chaining? I didn't actually realize it was even a feature.

@dcramer
Copy link
Member

dcramer commented Apr 3, 2015

Ignore that comment, I'm an idiot. The ticket actually points it out :)

@nateberkopec
Copy link
Contributor

Thanks! Will take a look.

@javawizard
Copy link
Contributor Author

Awesome. Just pushed up a fix to not check reporting when causes aren't supported.

exceptions.reverse!

exc_int.values = exceptions.map do |exc|
SingleExceptionInterface.new do |int|
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, I'm not really a fan of this name/a new class. Why can't you just use multiple instances of ExceptionInterface?

nateberkopec added a commit that referenced this pull request Apr 8, 2015
@nateberkopec nateberkopec merged commit d50a1e3 into getsentry:master Apr 8, 2015
@javawizard javawizard deleted the exception-chaining branch April 10, 2015 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support chained exceptions
3 participants