fix(gatsby): Use concrete type resolvers when filtering on node interface fields #16679
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.
When filtering on
@nodeInterface
fields, we currently use the resolver on the interface type. This PR changes this to use the resolver on the type returned from the interface'sresolveType
, which is in line with what graphql does when resolving the fields in the selection set.Related: #12272 (comment)
Fixes: #16890
Note: I tried to change as little as possible in
prepare-nodes
which will be replaced by @freiksenet's work in thematerialization
branch anyway.