Skip to content
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

Pessimistic Version Constraint for Memoist (~>) Causing Issues with Ruby Named Arguments #172

Open
brandon-carag opened this issue Jul 7, 2023 · 0 comments

Comments

@brandon-carag
Copy link

Currently, the Gemspec applies the pessimistic version constraint operator on Memoist:

https://github.com/projecttacoma/cqm-parsers/blob/master/cqm-parsers.gemspec#L31

Using this version of memoist causes the memoization of named arguments to break with a not-very-friendly error message: wrong number of arguments (given 1, expected 0; required keywords: example_argument

Many projects use memoist widely and if they want to use cqm-parsers, this version constraint may inadvertently break other areas of their app where invocations of methods with named arguments occur.

For historical context, named arguments were supported in Ruby starting in 2.0, which was released over 10 years ago. Do you think you could loosen the restriction on the Memoist gem such that it uses a ">=" operator?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant