-
-
Notifications
You must be signed in to change notification settings - Fork 397
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
end_with
takes the assumption that the receiver is a hash, or string.
#1025
Comments
Anyhow, if you want it to work with an object of your own, you can implement |
Something like ?
|
@TravisSpangle - the fix for this is going to require a change the (And sorry about the delayed response...) |
This addresses issue rspec#1025. With this change, the StartWith matcher will rely on an object's start_with? method if available. Similarly, the EndWith matcher will rely on an object's end_with? method if available. This is especially useful when a class implements start_with? but not the indexing operator, or end_with? but not the indexing operator.
This addresses issue rspec#1025. With this change, the StartWith matcher will rely on an object's start_with? method if available. Similarly, the EndWith matcher will rely on an object's end_with? method if available. This is especially useful when a class implements start_with? but not the indexing operator, or end_with? but not the indexing operator.
The text was updated successfully, but these errors were encountered: