This repository has been archived by the owner on Jul 20, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains 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
1 comment
on commit b4ab67c
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 don't disagree. It seems to be an issue with how RSpec internally raises exceptions. Relevant discussion: rspec/rspec-expectations#231
Specifically, rspec/rspec-expectations#231 (comment) has a good idea of whipping together a quick custom RSpec matcher.
I really hate this. It changes the intent of the spec, which is to make sure the implementing class actually implements the method. If that implementation raises another kind of exception, I don't care. If they are really deprecating this in new RSpec, I feel like there has to be an alternative somewhere.