avoid wrapping materialized fieldValueObject in a CompletableFuture #3943
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.
While updating graphql-kotlin to graphql-java 23 found that
completeField
is still wrappingFieldValueInfo.fieldValueObject
in aCompletableFuture
for objects already materialized / in memorythis might be considered a follow up of the
Completable Future wrapping
change set that came in graphql-java 22https://github.com/graphql-java/graphql-java/releases/tag/v22.0
I don't think this is a breaking change.