-
Notifications
You must be signed in to change notification settings - Fork 70
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
Fix one more keyword argument warning #251
Conversation
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.
Yes, unfortunately that method does not have tests... |
Is it possible to add a test, in this PR? |
Hmm, what would you like it to test? Anyway, I think it has been something like 10 years since I used Minitest last time, so would take me some time to study how to mock things etc. |
Thanks @tmatilai -- I don't actually receive any warnings before this change when running the test suite on Ruby 2.7. Should I? |
Oh sorry I misunderstood the last comment. There's no coverage so the tests don't show a warning. Don't worry about adding a test, I can do that. Happy to merge this @olleolleolle EDIT: I've added a test |
Thanks, everyone! Glad that we got good outcomes! |
Just fyi to other users: you can use |
Even better, thanks @leejarvis |
Update ruby-slop to 4.8.1. v4.8.1 (2020-03-31) ------------------- Bug fixes: * Fix keyword argument warning. [#251](leejarvis/slop#251)
At least one more warning escaped #248.