Repository navigation
Document the tools changes in 14.4.0 - #82
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs for what changed in graphql-java-tools 14.4.0.
DataFetchingEnvironment,GraphQLContextand the context class after the arguments, in any order (#888), and a resolver method can leave out the data class instance when it ends in one of those (#904). The old text said the environment "must be the last argument", which wasn't quite true anymore.SCALARmoves to the supported locations (#894), wirings run on the built schema (#895), and misused directives log a warning (#885).I left out the fixes that just make things work the way the docs already say they do.
Built it locally with Hugo 0.168.0 (same as the workflow). No errors, and the new link resolves.
🤖 Generated with Claude Code