Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Issues using `TypeResolver`, `BatchedExecutionStrategy` and `CompletableFuture` together

See original GitHub issue

It seems that if you’re using the BatchedExecutionStrategy and a DataFetcher that provides an interface type returns a CompletableFuture, the CompletableFuture rather than the raw value is passed to the TypeResolver for the interface.

Here is a test that demonstrates the issue.

Issue Analytics

State:
Created 6 years ago
Comments:9 (7 by maintainers)

Top GitHub Comments

1reaction

vincentDAOcommented, Sep 8, 2017

Great! We’re waiting to upgrade our app to 4.2.

1reaction

andimarekcommented, Sep 7, 2017

yes, we will do 4.2.

Top Results From Across the Web

graphql-java Documentation - Read the Docs

A TypeResolver helps graphql-java to decide which type a concrete value belongs to. ... You wire this together using this builder pattern.

Improving Performance with Java's CompletableFuture

In this article, we will learn how to use CompletableFuture to increase the performance of our application. We'll start with looking at the ......

Index (graphql-java 4.2 API) - javadoc.io

BatchedExecutionStrategy () - Constructor for class graphql.execution.batched. ... This allows you to chain together a number of Instrumentation ...

graphql-java Documentation Release stable - DocPlayer.net

A TypeResolver helps graphql-java to decide which type a concrete value belongs to. ... You wire this together using this builder pattern RuntimeWiring ......

Connect Concurrent Actions Using CompletableFutures

When we used a CountDownLatch as a barrier, the problem we were trying ... You can pipeline different steps together using just the...