Schema mapping should inspect fields that have a matching class property #934
Comments
rstoyanchev
added a commit
that referenced
this issue
Mar 26, 2024
Rather than passing a DataFetcher into checkField, determine the return type externally and pass it in. That makes the method more generally useful, and independent of how the associated type is determined, e.g. whether from a DataFetcher return type or a corresponding Java property. See gh-934
rstoyanchev
added a commit
that referenced
this issue
Mar 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently schema mapping does not inspect fields that have a matching class property, and generally there is nothing further to do if the field is a scalar or enum, which is the most likely case. However, if the field is a type that contains other fields, then we have to go further. It is an unlikely scenario that implies eager fetching, but from the perspective of schema inspection we need to go as far as we can and depending on what we find.
The text was updated successfully, but these errors were encountered: