Package org.allGraphQLCases.server.impl.relayConnection

Class DataFetchersDelegateHumanConnectionImpl

java.lang.Object
org.allGraphQLCases.server.impl.relayConnection.DataFetchersDelegateHumanConnectionImpl
All Implemented Interfaces:
DataFetchersDelegateHumanConnection
@Component public class DataFetchersDelegateHumanConnectionImpl extends Object implements DataFetchersDelegateHumanConnection

  • Constructor Details

    • DataFetchersDelegateHumanConnectionImpl

      public DataFetchersDelegateHumanConnectionImpl()

  • Method Details

    • edges

      public List<STP_HumanEdge_STS> edges(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_HumanConnection_STS origin)
      Description copied from interface: DataFetchersDelegateHumanConnection
      This method loads the data for HumanConnection.edges. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a List<org.allGraphQLCases.server.STP_HumanEdge_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<List<org.allGraphQLCases.server.STP_HumanEdge_STS>> or a Flux<List<org.allGraphQLCases.server.STP_HumanEdge_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<List<org.allGraphQLCases.server.STP_HumanEdge_STS>>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<List<org.allGraphQLCases.server.STP_HumanEdge_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:
      edges in interface DataFetchersDelegateHumanConnection
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the edges attribute of the origin, which is an instance of {ObjectType {name:HumanConnection, fields:{Field{name:edges, type:[HumanEdge], params:[]},Field{name:pageInfo, type:PageInfo!, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • pageInfo

      public STP_PageInfo_STS pageInfo(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_HumanConnection_STS origin)
      Description copied from interface: DataFetchersDelegateHumanConnection
      This method loads the data for HumanConnection.pageInfo. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_PageInfo_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_PageInfo_STS> or a Flux<org.allGraphQLCases.server.STP_PageInfo_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_PageInfo_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_PageInfo_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:
      pageInfo in interface DataFetchersDelegateHumanConnection
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the pageInfo attribute of the origin, which is an instance of {ObjectType {name:HumanConnection, fields:{Field{name:edges, type:[HumanEdge], params:[]},Field{name:pageInfo, type:PageInfo!, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.