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

Avoid reraising exceptions #16

Merged
merged 1 commit into from
Jul 9, 2019
Merged

Conversation

jeremyevans
Copy link
Contributor

Instead of raising a new exception with a modified message, just
use the correct message to begin with. This avoids the issue with
both exceptions being displayed at error exit.

This is an alternative approach to solving the issue in #14.

Instead of raising a new exception with a modified message, just
use the correct message to begin with.  This avoids the issue with
both exceptions being displayed at error exit.
@ioquatix
Copy link
Member

ioquatix commented Jul 9, 2019

This makes sense to me.

@nobu, what you think can we merge?

@ioquatix
Copy link
Member

ioquatix commented Jul 9, 2019

This LGTM.

@ioquatix ioquatix merged commit 2d46b79 into ruby:master Jul 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants