Update check ensuring federated types have @EntityMapping
to exempt entities with 'resolvable: false', since by definition
those should not have an @EntityMapping.
See gh-1225
Signed-off-by: Josh Allen <joshuapaulallen@gmail.com>
WebGraphQlRequest already implements ExecutionGraphQlRequest through
its parent class DefaultExecutionGraphQlRequest, making the explicit
interface declaration redundant.
See gh-1218
Signed-off-by: do.vantrinh <do.vantrinh@moneyforward.co.jp>
Prior to this commit, error handling methods would support various
arguments, including the exception being handled.
Our reference documentation would advise to create a new instance of a
`GraphQLError` using `GraphQLError.newError()`. This does not initialize
the location and path information of the current error.
This commit allows error handling methods to get injected with a
`GraphQlErrorBuilder<?>` argument that is initialized with the current
`DataFetchingEnvironment` (thus filling the location and path parts).
Fixes gh-1200
This commit sets the new GraphQL Java baseline to 24.0 for this Spring
for GraphQL generation.
This also uses the new `DataLoader#getName` property in the batch loader
registry and the observability instrumentation.
Closes gh-1210
Closes gh-1211
ContextDataFetcherDecorator was not retaining extensions for DataFetchers returning
a DataFetcherResult instance.
Closes gh-1199
Signed-off-by: Patrick Strawderman <pstrawderman@netflix.com>
[brian.clozel@broadcom.com: apply code conventions]
Signed-off-by: Brian Clozel <brian.clozel@broadcom.com>
Prior to this commit, the `GraphQlArgumentBinder` would choose between
two strategies:
* if there is a constructor with arguments, instantiate the target and
bind it using the constructor
* otherwise, use the default constructor and use bean properties binding
This commit extends the first case and attempts to further bind bean
properties after constructor instantiation.
Closes gh-1163
