Support for new GraphQL Interpreter about batch-loader

[ro-savage]

Thanks @exAspArk - came across the today and updating all our resolvers to use BatchLoader::GraphQL.for fixed it.

[exAspArk]

Hey @JanStevens!

Thank you for sharing the link. I'll be able to take a look into it once the Interpreter became a default runtime and became more stable (not experimental to avoid potential breaking changes in BatchLoader).

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[bessey]

@exAspArk, does this work now? I mean, we're just starting to use this gem on a grapqhl-ruby 1.9 project and it seems to work, but thought i'd confirm since I see nothing in the changelogs.

[exAspArk]

It seems like GraphQL::Execution::Interpreter is now considered stable since graphql gem version 1.10+ (January 2020). I'm reopening the issue, will try to make it work 🙏

[exAspArk]

@exAspArk, does this work now? I mean, we're just starting to use this gem on a grapqhl-ruby 1.9 project and it seems to work, but thought i'd confirm since I see nothing in the changelogs.

Long story short:

• if you use BatchLoader::GraphQL.for, then you're fine 👍
• if you use BatchLoader.for and Interpreter, then you'd need to use #62 (draft PR)
• if you use BatchLoader.for without Interpreter, then it works with all GraphQL versions except the range between 1.8.7 rmosolgo/graphql-ruby#1778 - 1.8.10 #26 (comment)

I.e. please use BatchLoader::GraphQL.for

I'm going to deprecate using BatchLoader.for in GraphQL, which adds unnecessary coupling with the graphql gem. Alternatively, it's possible to keep BatchLoader.for and wrap it:

field :user, UserType, null: false

def user # resolver
  BatchLoader::GraphQL.wrap(lazy_user)
end

def lazy_user
  BatchLoader.for...
end

[exAspArk]

I released a new version which still keeps compatibility with BatchLoader.for + GraphQL with Interpreter, but adds a deprecation warning. More info in the changelog.