Open
Conversation
Owner
|
I think this is very likely to be a good idea. However I suspect it may have to be a 'major' version release / API breaking change - some people might be depending on it not being a StandardError in their code. |
Author
|
You're right here. |
|
+1 |
|
+1, this is a change worth making. |
|
👍 This change would have saved me hours (days?) of debugging. |
This file contains hidden or 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
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.
Thanks for the nice library.
I think that exceptions should be derived from the ruby
StandardError. This makes it possible to rescue them in a general rescue block.It will result in the following code to work as expected: