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>
This commit switches to using Java 24 as the mai JVM in the GitHub
action and also configures the foojay resolver for Java toolchain
resolution by Gradle.
See gh-1206
This rule flags valid usages because it conflates annotated methods and
annotated return types, considering that the `@Nullable` annotation
should be on its own line. For example, the following fails:
```
@Override
@Nullable String getName() {
```
See gh-1132
This commit removes the new deprecated
`org.springframework.lang.Nullable` annotations and replaces them with
JSpecify equivalents.
Note, because those new annotations are applied on type usage, this
commit not only renames imports, but also moves annotations close to the
nullable usage types.
Closes gh-1132
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
