-
-
Notifications
You must be signed in to change notification settings - Fork 32
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 Ruby 2.7 warning: Using the last argument as keyword parameters i… #56
Conversation
I believe the But it might be worth a try doing just the double splat version, and seeing if it passes CI? I think it may. So you may not need the ugly conditional, double splat can, I suspect, work in all supported versions. Alternately, if it does need a conditional, I think double-splat will work further back than 2.7. |
Thanks, trying that. |
@jrochkind Thanks for the review and helping out! ❤️ @abhinavs Thanks for fixing the warnings. ❤️ I'm currently going through |
no problem, in fact, thanks a lot for creating tty and tty plugins - design is very clean. Just created blockr - used tty, tty-file and tty-command to create it. I am still exploring, will be building a few more command line apps. |
@abhinavs |
looks very intuitive and very readable - will definitely try it out. Thanks @piotrmurach |
Describe the change
Ruby 2.7 warning: "Using the last argument as keyword parameters is deprecated"
Why are we doing this?
In Ruby 2.7, the way ruby handles the positional arguments and keyword arguments is changed, aiming to provide a smooth transition to Ruby 3. This has resulted in warnings on the command line when one uses cmd.run.
Benefits
This will remove the warning message which is thrown
Drawbacks
Requirements
Put an X between brackets on each line if you have done the item:
[] Tests written & passing locally?
[] Code style checked?
[] Rebased with
master
branch?[] Documentation updated?