-
Notifications
You must be signed in to change notification settings - Fork 52
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
Incompatibility with graphql-ruby 2.0.18+ #87
Comments
I'm also seeing this issue in my application. I am working around it for the moment by locking the
|
Is it broken specifically with that version, or with all onwards versions? (did graphql-rb revert this?) |
There are other breaking changes too, with graphql 2.2.5, I see
|
Sorry, I don't have the bandwidth to address this issue right now. Please feel free to submit a pull request, and I'd be happy to review and merge it 🙏 |
It seems that applying:
is enough to make the test suite pass with ruby3.1 |
It seems there was a breaking change introduced in 2.0.18 that causes
use BatchLoader::GraphQL
to cause the following exception:The text was updated successfully, but these errors were encountered: