Interface DataFetchersDelegateAnotherMutationType

All Known Implementing Classes:
DataFetchersDelegateAnotherMutationTypeImpl

public interface DataFetchersDelegateAnotherMutationType
This interface contains the fata fetchers that are delegated in the bean that the implementation has to provide, when fetching fields for the AnotherMutationType GraphQL type, as defined in the provided GraphQL schema. Please read the wiki server page for more information on this.
Author:
generated by graphql-java-generator
See Also:
  • Method Summary

    Modifier and Type
    Method
    Description
    _if(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment)
    Description for the if field:
    test for issue #139 (use of java reserved keyword)
    This method loads the data for AnotherMutationType.if.
    _implements(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment)
    This method loads the data for AnotherMutationType.implements.
    createAllFieldCases(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SINP_AllFieldCasesInput_SINS input)
    This method loads the data for AnotherMutationType.createAllFieldCases.
    createHuman(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SINP_HumanInput_SINS human)
    This method loads the data for AnotherMutationType.createHuman.
    deleteSnacks(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, List<UUID> id)
    Description for the deleteSnacks field:
    Tests for issue 51
    This method loads the data for AnotherMutationType.deleteSnacks.
  • Method Details

    • createHuman

      Object createHuman(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SINP_HumanInput_SINS human)
      This method loads the data for AnotherMutationType.createHuman. 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
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      human - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.
    • createAllFieldCases

      Object createAllFieldCases(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SINP_AllFieldCasesInput_SINS input)
      This method loads the data for AnotherMutationType.createAllFieldCases. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_AllFieldCases_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_AllFieldCases_STS> or a Flux<org.allGraphQLCases.server.STP_AllFieldCases_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_AllFieldCases_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_AllFieldCases_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
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      input - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.
    • deleteSnacks

      Object deleteSnacks(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, List<UUID> id)
      Description for the deleteSnacks field:
      Tests for issue 51
      This method loads the data for AnotherMutationType.deleteSnacks. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a java.lang.Boolean)
      • 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<java.lang.Boolean> or a Flux<java.lang.Boolean>
      • 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<java.lang.Boolean>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<java.lang.Boolean>. 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
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      id - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.
    • _if

      Object _if(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment)
      Description for the if field:
      test for issue #139 (use of java reserved keyword)
      This method loads the data for AnotherMutationType.if. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a java.lang.String)
      • 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<java.lang.String> or a Flux<java.lang.String>
      • 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<java.lang.String>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<java.lang.String>. 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
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.
    • _implements

      Object _implements(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment)
      This method loads the data for AnotherMutationType.implements. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a java.lang.String)
      • 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<java.lang.String> or a Flux<java.lang.String>
      • 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<java.lang.String>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<java.lang.String>. 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
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.