Remove obsolete NoMethodError compatibility#5670
Merged
rmosolgo merged 1 commit intoJul 15, 2026
Merged
Conversation
Owner
|
🎉 |
Owner
|
Btw, I'm open to bringing this gem up to 3.0 -- removing support for 2.7. I think there some conditionals for that, too. I'd welcome your contribution if you're interested! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
My understanding is that this gem supports Ruby 2.7 and later, so support for version 2.2 is likely no longer necessary.
graphql-ruby/graphql.gemspec
Line 16 in c30cc15
I have tried removing the code that appears to be obsolete. What do you think?