Package org.allGraphQLCases.server.impl.relayConnection

Class DataFetchersDelegateHumanEdgeImpl

java.lang.Object

org.allGraphQLCases.server.impl.relayConnection.DataFetchersDelegateHumanEdgeImpl

All Implemented Interfaces:

DataFetchersDelegateHumanEdge

@Component
public class DataFetchersDelegateHumanEdgeImpl
extends Object
implements DataFetchersDelegateHumanEdge

Constructor Summary

Constructors

Constructor	Description
DataFetchersDelegateHumanEdgeImpl()

Method Summary

Modifier and Type	Method	Description
CompletableFuture<STP_Human_STS>	node(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_HumanEdge_STS origin)	This method loads the data for HumanEdge.node.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

DataFetchersDelegateHumanEdgeImpl

public DataFetchersDelegateHumanEdgeImpl()

Method Details

node

public CompletableFuture<STP_Human_STS> node(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment,
 org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader,
 STP_HumanEdge_STS origin)

Description copied from interface: DataFetchersDelegateHumanEdge

This method loads the data for HumanEdge.node. It may return whatever is accepted by the Spring Controller, that is:

• A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
• Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
• Kotlin coroutine and Flow are adapted to Mono and Flux
• java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>

As a complement to the spring-graphql documentation, you may also return:

• A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
• A Publisher (instead of a Flux), for Subscription for instance

Specified by:

node in interface DataFetchersDelegateHumanEdge

Parameters:

dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher

dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
You'll find more informations here: https://github.com/graphql-java/java-dataloader

origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the node attribute of the origin, which is an instance of {ObjectType {name:HumanEdge, fields:{Field{name:node, type:Human, params:[]},Field{name:cursor, type:String!, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.