Bump graphql-java from 17.0 to 18.0

[dependabot]

Bumps graphql-java from 17.0 to 18.0.

Release notes

Sourced from graphql-java's releases.

18.0

We are happy to announce v18.0 of graphql-java

https://github.com/graphql-java/graphql-java/pulls?q=is%3Apr+milestone%3A18.0+is%3Aclosed

Applied Directives

Graphql directives have two modes. They can be defined in a schema

directive @example on FIELD_DEFINITION | ARGUMENT_DEFINITION

and they can be applied to schema elements and query elements

type Query {
   field(arg : String! ) @example

So we have a directive definition and cases where that directive is applied to an element.

However when the graphql.schema.GraphQLDirective and graphql.schema.GraphQLArgument classes was created, we modelled this badly. These classes should really represent a directive definition in schema only but we reused them to also be the representation of a directive and value arguments applied to another schema or query element.

This modelling is wrong. You can tell because we have javadoc comments like this in graphql.schema.GraphQLArgument saying a certain property is only applicable in certain call contexts.

    /**
     * This is only used for applied directives, that is when this argument is on a {@link GraphQLDirective} applied to a schema or query element
     *
     * @return an input value with state for an applied directive
     *
     * @deprecated use {@link GraphQLAppliedDirectiveArgument} instead
     */
    @Deprecated
    public @NotNull InputValueWithState getArgumentValue() {
        return value;
    }

So we have decided to fix this bad class modelling in version 18. We have introduced new classes

• graphql.schema.GraphQLAppliedDirective
• graphql.schema.GraphQLAppliedDirectiveArgument

which represent an applied directive on a schema element and

• graphql.execution.directives.QueryAppliedDirective
• graphql.execution.directives.QueryAppliedDirectiveArgument

... (truncated)

Commits

• 470811b Update README.zh_cn.md (#2758)
• e973c9a Merge pull request #2749 from graphql-java/make_values_lazy_in_esi
• f67e3f1 Merge pull request #2738 from graphql-java/2736-fix-dfe-selectionset-conditio...
• dcaafad fix tests
• aafe5ff Update src/main/java/graphql/normalized/ExecutableNormalizedField.java
• a81ed90 Update src/main/java/graphql/normalized/ExecutableNormalizedField.java
• 08756b4 Update src/main/java/graphql/normalized/ExecutableNormalizedField.java
• 88198e1 Make ExecutionStepInfo values be lazy
• 0b887a9 This is some performance optimisations for NormalisedOperations (#2732)
• 00f9e8b rework ENF isCondition and adapt DFSelectionSet
• 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 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)

[dependabot]

Superseded by #224.