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

🔇 Fix ruby 2.7 warnings #304

Merged
merged 3 commits into from
Jun 22, 2024
Merged

🔇 Fix ruby 2.7 warnings #304

merged 3 commits into from
Jun 22, 2024

Conversation

nevans
Copy link
Collaborator

@nevans nevans commented Jun 22, 2024

Other than backports, maybe, these should be the last ruby 2.7 workarounds we need to make before raising the minimum ruby requirement to 3.1 (#276).

This looks like it was added for debugging, but it's unassigned and
unused now.  Future debuggers can easily add it back as needed.
There is _some_ value in testing that it works even without this change.
But the main purpose of the test is simply testing the conversion from a
hash parameter.  Forcing the kwargs to be empty is fine.

Other than backports, maybe, this is the last ruby 2.7 concession I'll
be making before we raise the minimum ruby requirement.  😄
@nevans nevans merged commit f1762fd into master Jun 22, 2024
26 checks passed
@nevans nevans deleted the fix-ruby-2.7-warnings branch June 22, 2024 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant