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

Make Sniffer work with Ruby 3.0 separation of kw args #3

Merged
merged 1 commit into from
Jan 22, 2021

Conversation

danmarcab
Copy link
Contributor

With the release of ruby 3.0 (https://www.ruby-lang.org/en/news/2020/12/25/ruby-3-0-0-released/)
keyword and positional arguments are separated (https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/)

In this case we need to explicitly pass a hash to the increment
methods.

With the release of ruby 3.0 (https://www.ruby-lang.org/en/news/2020/12/25/ruby-3-0-0-released/)
keyword and positional arguments are separated (https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/)

In this case we need to explicitly pass a hash to the increment
methods.
@danmarcab
Copy link
Contributor Author

CI is failing due to rubocop saying it doesn't support ruby version 2.3 (specified in gemspec). Not sure what to do there (updating gemspec to 2.4 works but not sure if that's ok), please advise.

@Envek Envek merged commit 4a93326 into yabeda-rb:master Jan 22, 2021
@Envek
Copy link
Member

Envek commented Jan 22, 2021

Thank you very much! I will release new version a bit later.

I decided to drop EOLed Rubies (anyway Sniffer requires at least 2.5) /cc @dsalahutdinov

And now CI passes! ;-)

@Envek
Copy link
Member

Envek commented Jan 25, 2021

Released in 0.2.0, thanks!

@danmarcab
Copy link
Contributor Author

Awesome, thanks @Envek !

@danmarcab danmarcab deleted the support-ruby-3 branch January 25, 2021 19:20
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

Successfully merging this pull request may close these issues.

2 participants