Package org.allGraphQLCases.server.impl

Class DataFetchersDelegateReservedJavaKeywordAllFieldCasesImpl

java.lang.Object
org.allGraphQLCases.server.impl.DataFetchersDelegateReservedJavaKeywordAllFieldCasesImpl
All Implemented Interfaces:
DataFetchersDelegateReservedJavaKeywordAllFieldCases
@Component public class DataFetchersDelegateReservedJavaKeywordAllFieldCasesImpl extends Object implements DataFetchersDelegateReservedJavaKeywordAllFieldCases

  • Constructor Details

    • DataFetchersDelegateReservedJavaKeywordAllFieldCasesImpl

      public DataFetchersDelegateReservedJavaKeywordAllFieldCasesImpl()

  • Method Details

    • _implements

      public CompletableFuture<SIP_WithID_SIS> _implements(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,SIP_WithID_SIS> dataLoader, STP_ReservedJavaKeywordAllFieldCases_STS origin)
      Description copied from interface: DataFetchersDelegateReservedJavaKeywordAllFieldCases
      Description for the implements field:
      A field with a java reserved name which is an interface
      This method loads the data for ReservedJavaKeywordAllFieldCases.implements. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.SIP_WithID_SIS)
      • 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.SIP_WithID_SIS> or a Flux<org.allGraphQLCases.server.SIP_WithID_SIS>
      • 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.SIP_WithID_SIS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.SIP_WithID_SIS>. 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:
      _implements in interface DataFetchersDelegateReservedJavaKeywordAllFieldCases
      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 implements attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAllFieldCases, fields:{Field{name:if, type:Unit, params:[]},Field{name:nonJavaKeywordField, type:WithID, params:[]},Field{name:implements, type:WithID, params:[]},Field{name:import, type:String, params:[]},Field{name:instanceof, type:MyCustomScalarForADate, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:AnyCharacter, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • _int

      public CompletableFuture<STP_Human_STS> _int(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAllFieldCases_STS origin)
      Description copied from interface: DataFetchersDelegateReservedJavaKeywordAllFieldCases
      Description for the int field:
      A field with a java reserved name which is an object type
      This method loads the data for ReservedJavaKeywordAllFieldCases.int. 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:
      _int in interface DataFetchersDelegateReservedJavaKeywordAllFieldCases
      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 int attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAllFieldCases, fields:{Field{name:if, type:Unit, params:[]},Field{name:nonJavaKeywordField, type:WithID, params:[]},Field{name:implements, type:WithID, params:[]},Field{name:import, type:String, params:[]},Field{name:instanceof, type:MyCustomScalarForADate, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:AnyCharacter, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • _interface

      public SUP_AnyCharacter_SUS _interface(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_ReservedJavaKeywordAllFieldCases_STS origin)
      Description copied from interface: DataFetchersDelegateReservedJavaKeywordAllFieldCases
      Description for the interface field:
      A field with a java reserved name which is a union
      This method loads the data for ReservedJavaKeywordAllFieldCases.interface. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.SUP_AnyCharacter_SUS)
      • 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.SUP_AnyCharacter_SUS> or a Flux<org.allGraphQLCases.server.SUP_AnyCharacter_SUS>
      • 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.SUP_AnyCharacter_SUS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.SUP_AnyCharacter_SUS>. 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:
      _interface in interface DataFetchersDelegateReservedJavaKeywordAllFieldCases
      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 interface attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAllFieldCases, fields:{Field{name:if, type:Unit, params:[]},Field{name:nonJavaKeywordField, type:WithID, params:[]},Field{name:implements, type:WithID, params:[]},Field{name:import, type:String, params:[]},Field{name:instanceof, type:MyCustomScalarForADate, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:AnyCharacter, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • nonJavaKeywordField

      public CompletableFuture<SIP_WithID_SIS> nonJavaKeywordField(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,SIP_WithID_SIS> dataLoader, STP_ReservedJavaKeywordAllFieldCases_STS origin)
      Description copied from interface: DataFetchersDelegateReservedJavaKeywordAllFieldCases
      Description for the nonJavaKeywordField field:
      A field with a _non_ java reserved name which is an interface (to check standard behavior)
      This method loads the data for ReservedJavaKeywordAllFieldCases.nonJavaKeywordField. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.SIP_WithID_SIS)
      • 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.SIP_WithID_SIS> or a Flux<org.allGraphQLCases.server.SIP_WithID_SIS>
      • 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.SIP_WithID_SIS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.SIP_WithID_SIS>. 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:
      nonJavaKeywordField in interface DataFetchersDelegateReservedJavaKeywordAllFieldCases
      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 nonJavaKeywordField attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAllFieldCases, fields:{Field{name:if, type:Unit, params:[]},Field{name:nonJavaKeywordField, type:WithID, params:[]},Field{name:implements, type:WithID, params:[]},Field{name:import, type:String, params:[]},Field{name:instanceof, type:MyCustomScalarForADate, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:AnyCharacter, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.