-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 Spree::MigrationHelpers Ruby 3.0 compatible #5072
Make Spree::MigrationHelpers Ruby 3.0 compatible #5072
Conversation
a731995
to
5ad08b6
Compare
@kennyadsl previously discussed on Slack, that we might want to remove this logic from Solidus as it's not used by Solidus. I agree with the idea that stores should be responsible for maintaining their own migration logic. WDYT? Should I make a new PR to deprecate the module and its methods? |
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.
Thanks @RyanofWoods! I'm good as is, but I left a suggestion. 🙏
Due to the separation of positional and keyword arguments in Ruby 3.0, the options default value of a hash cannot be coerced into keyword arguments.
5ad08b6
to
3568af9
Compare
Please backlog to supported versions: v3.4, v3.3 and v3.2. Though note, this will mean v3.1 which is now unsupported will have a breaking change as this is the Solidus version where Ruby 3.0 became supported. |
@RyanofWoods we could backport this change to the 3.1 branch in GH (people could still reference to it) without releasing a new version. |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
[v3.4] Merge pull request #5072 from nebulab/ryanofwoods/make-migration-helper-ruby-3-compatible
Summary
Due to the separation of positional and keyword arguments in Ruby 3.0, the options default value of a hash can no longer be coerced into keyword arguments. Using double splat avoids this by only allowing optional arguments as keywords.
Checklist
Check out our PR guidelines for more details.
The following are mandatory for all PRs:
The following are not always needed: