Honor the default execution engine in Query#result - #5742
Merged
rmosolgo merged 1 commit intoSep 16, 2026
Merged
Conversation
Owner
|
Thanks! |
This was referenced Sep 21, 2026
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.
Schema.executehonorsdefault_execution_next, butQuery#resultalways invokesExecution::Interpreterdirectly.As a result, manually constructed queries ignore a schema configured with:
This is especially visible with Next-specific field resolution such as resolve_static: or resolve_batch:. The same query succeeds through Schema.execute, but GraphQL::Query.new(...).result runs the legacy resolver path and raises a missing-method error.
This PR makes Query#result select Execution::Next or Execution::Interpreter from the schema's default execution setting. Schemas that retain the legacy default continue using the interpreter.