-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
Ruby 2.7+ compatibility (keyword arguments) #85
Comments
thbar
added a commit
that referenced
this issue
Feb 4, 2020
thbar
added a commit
that referenced
this issue
Feb 4, 2020
This adds support for all component types.
I've started working on proper support on branch |
This was referenced Feb 5, 2020
thbar
changed the title
Investigate warnings with Ruby 2.7+
Ruby 2.7+ compatibility (keyword arguments)
Feb 5, 2020
|
thbar
added a commit
that referenced
this issue
Sep 14, 2020
thbar
added a commit
that referenced
this issue
Sep 14, 2020
This adds support for all component types.
Ruby 2.7 compatibility is available in A new release will be published later with corresponding changes. |
Release v3.5.0 has been published. Closing! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Due to the recent changes announced here:
https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/
(and tracked here initially https://bugs.ruby-lang.org/issues/14183)
it is possible to get warnings (and later with Ruby 2.8+, most likely errors), depending on how the components are implemented (and this is the case with
kiba-common
, for instance).I'm opening this issue to track this down.
For now I would recommend to stick with Ruby 2.6 if possible.
The text was updated successfully, but these errors were encountered: