Bump com.graphql-java:graphql-java from 24.3 to 25.0

[dependabot]

Bumps com.graphql-java:graphql-java from 24.3 to 25.0.

Release notes

Sourced from com.graphql-java:graphql-java's releases.

25.0

Key changes

Dataloader

Refactoring strategy

The existing PerLevelDataLoaderStrategy has been refactored which lead to simplifications and performance improvements.

New strategies

Two new strategies were introduced: CHAINED and EXHAUSTED. Both can be configured via UnusalConfiguration (see next section).

CHAINED allow for chained DataLoaders to be used while keeping a per level dispatch strategies.

EXHAUSTED is a completely new strategy that works on the basis to dispatch once the engine is not busy. It mirrors the JS data loader dispatch strategy, but for a multi threaded system.

Unusual Configuration

A more generalised configuration mechanism has been added for "unusual configuration". By that we mean configuation we dont expect many people to use but if they do its now in a more common place

For example if you wanted to change the maximum depth the document parser will accept you could call the following methods.

        var parserOptions = newParserOptions().maxRuleDepth(99).build()
        GraphQL.unusualConfiguration().parsing().setDefaultParserOptions(parserOptions)

JSpecify Annotations

The team are starting to embrace https://jspecify.dev/ annotations as the way to indicate nullable and non nullable fields. Many important classes have had these annotations added to help make it more semantically clear when a value can be null or not.

Breaking Changes

A wrapping FetchedValue object is not always returned on field fetchers for performance reasons. This means that graphql.execution.instrumentation.parameters.InstrumentationFieldCompleteParameters#getFetchedObject was created to replace the older getFetchedValue method and the returns object can sometimes be a FetchedValue or sometimes a simple POJO value.

Performance improvements

A series of performance improvements have been made to reduce the memory footprint of the library. Also the Java .stream() operator can be slower than a more direct loop and many of these calls have been changed for performance reasons.

• avoid wrapping materialized fieldValueObject in a CompletableFuture by @​samuelAndalon in graphql-java/graphql-java#3943
• ExecutionStrategyParameters now has a direct transform without a Builder by @​bbakerman in graphql-java/graphql-java#3935
• ExecutionStepInfo now has a direct transform without a Builder by @​bbakerman in graphql-java/graphql-java#3934
• FpKit now longer uses streams for performance reasons by @​bbakerman in graphql-java/graphql-java#3932
• Implement toString/hashCode/equals for DataFetcherResult by @​AlexandreCarlton in graphql-java/graphql-java#3964

... (truncated)

Commits

• 76832a4 Add performance results for commit bbe6a653939113bedffe947fbf70315ff448f127
• bbe6a65 Merge pull request #4157 from graphql-java/update-java-dataloader
• 7031555 upgrade to dataloader 6
• 6b68072 upgrade to dataloader 6
• b3b3bea upgrade to dataloader 6
• 8dc1bee Add performance results for commit 6ce63f3531d032fa4c15ea8d5b4c4c3bbf0a95b7
• 7de429d Add performance results for commit 6ce63f3531d032fa4c15ea8d5b4c4c3bbf0a95b7
• 6ce63f3 Merge pull request #4161 from graphql-java/dependabot/gradle/com.fasterxml.ja...
• 2b2735d Merge pull request #4163 from graphql-java/dependabot/github_actions/EnricoMi...
• ead1587 Add performance results for commit 71e6199af4a1fd32da0685cd24093765b47cead1
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)