| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| README.md | 2026-10-23 | 1.7 kB | |
| v14.5.0 source code.tar.gz | 2026-10-23 | 145.6 kB | |
| v14.5.0 source code.zip | 2026-10-23 | 219.6 kB | |
| Totals: 3 Items | 366.9 kB | 0 | |
Deprecations
SchemaParserOptions.Builder.introspectionEnabled(...)and theintrospectionEnabledproperty are deprecated and will be removed in 15.0.0 (#910, [#858]). The option hides every field of the introspection types, like graphql-java'sNoIntrospectionGraphqlFieldVisibilitythat was deprecated in graphql-java 22. Turn introspection off with graphql-java instead:kotlin // for the whole JVM Introspection.enabledJvmWide(false) // per request ExecutionInput.newExecutionInput() .query(query) .graphQLContext(mapOf(Introspection.INTROSPECTION_DISABLED to true))An introspection query then fails with an "introspection disabled" error when it runs, instead of theFieldUndefinedvalidation error it gets with the option.
Behaviour changes
- Repeated fields (#920): a field that an object or input type declares twice, in the type and an extension, in two extensions or inside one definition, now logs a WARN from
graphql.kickstart.tools.SchemaParserthat names the declaration the schema keeps. Which one is kept doesn't change: objects keep the last one, input types keep their own over an extension's. ⚠️ This becomes an error in 15.0.0 (#865).
What's Changed
- Version Release by @github-actions[bot] in https://github.com/graphql-java-kickstart/graphql-java-tools/pull/907
- Deprecate the introspectionEnabled option by @oryan-block in https://github.com/graphql-java-kickstart/graphql-java-tools/pull/910
- Warn about a field that an object or input type declares twice by @oryan-block in https://github.com/graphql-java-kickstart/graphql-java-tools/pull/920
Full Changelog: https://github.com/graphql-java-kickstart/graphql-java-tools/compare/v14.4.0...v14.5.0