Closed olleolleolle closed 4 years ago
I would advise that this is hard-blocked
by the issues in cucumber / cucumber-core repos.
https://github.com/cucumber/cucumber-ruby-core/issues/187 https://github.com/cucumber/cucumber/issues/843
@luke-hill Both of these issues are closed.
Since the cucumber-ruby
gem is in 4.0 Release Candidate state for over a year, may I suggest to consider at least releasing a cucumber-rails
RC version, with the latest and greatest cucumber
(RC) and cucumber-core
?
This lag is beginning to have an impact on productivity, I guess not only for me.
I opened https://github.com/cucumber/cucumber-ruby/issues/1417 hoping to at least get some sense of how much longer it will take.
@DannyBen This issue is now hard blocked on #466 and I suggest once #466 is released we can probably close this as no longer relevant / fixed.
as for getting cucumber ruby 4 support in cucumber rails, This was done recently in the Open Source work. However it's anticipated some small issues might come crawling out.
@mvz You've gotten #466 merged - and I just checked, no warnings are showing in the Job
Yay!
Summary
We want to be compatible with current Ruby versions. 2.7 is not yet in the matrix. It could be.
Expected Behavior
Current Behavior
Possible Solution
Context & Motivation
Rails is moving forwards with their warnings-removal work for 2.7. This is a Rails plugin. Would be nice to move in the same direction.