-
Notifications
You must be signed in to change notification settings - Fork 23
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 arity check for keyword arguments #12
Conversation
test/support/features.rb
Outdated
Gem::Version.new(RUBY_VERSION) >= Gem::Version.new("2.0.0") | ||
end | ||
|
||
def required_keyword_args? |
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 would be willing to drop ruby 2.0.0 support to reduce code complexity
looks like there are some failures on jruby. If you don't want to fix those that is fine I'll try to fix it |
Previously keyword arguments were ignored, which prevented them from being passed in. This at least allows them to be passed in by treating them as a single optional or required argument. However, it doesn't yet check that a hash is passed in for the keyword arguments or that the hash has the expected keys.
2c40c59
to
de9e647
Compare
de9e647
to
2eae13e
Compare
For some reason I am not able to reproduce the jruby failures locally. However, it looks like the failures isn't happening after rebasing on top of #11 |
ruby 2.0 support has been dropped to simplify the code and tests are passing. Are there any other concerns? |
Thanks for the contribution I'll make a push now or when I get home |
@dylanahsmith pushed! |
Fixes #9
Previously keyword arguments were ignored, which prevented them from being passed in. This at least allows them to be passed in by treating them as a single optional or required argument. However, the code doesn't yet check that a hash is passed in for the keyword arguments or that the hash has the expected keys.