-
-
Notifications
You must be signed in to change notification settings - Fork 327
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
Support rails 7.1 #575
Support rails 7.1 #575
Conversation
Removes ``` DEPRECATION WARNING: Setting action_dispatch.show_exceptions to false is deprecated. Set to :none instead. (called from call at /home/runner/work/cucumber-rails/cucumber-rails/lib/cucumber/rails/action_dispatch.rb:14) ```
Rails 7.1 introduces a new "Raise error on missing only unless" feature (see rails/rails#43487). The new feature is enabled by default. I rewrote the auto-generated code in feature specs to comply to the new rule.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are carefully-worded, nice changes!
Can we add a changelog entry for this please as it's quite a big change @mgrunberg |
@luke-hill is #578 enough? I can change the message content if not. Also, would you consider releasing 3.0.0.rc.2? |
I'm looking to release v3 proper soon. We got about 1/2 to 2/3rds of the stuff in the rc1 release. There was only 2 big things I wanted to do else. One is on a branch I asked a couple of people to look at. Also I want to try leave the rc1 out for a bit to ensure nothing is completely goosed there. |
@luke-hill is now a good time for 3.0.0.rc.2? |
🤔 What's changed?
Use symbols to set
show_exceptions
in Rails 7.1+ and run test against Rails 7.1⚡️ What's your motivation?
I get a deprecation warning about the usage of a boolean with
show_exceptions
🏷️ What kind of change is this?
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.