Package org.allGraphQLCases.server.impl

Class DataFetchersDelegateAllFieldCasesInterfaceImpl

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

  • Constructor Details

    • DataFetchersDelegateAllFieldCasesInterfaceImpl

      public DataFetchersDelegateAllFieldCasesInterfaceImpl()

  • Method Details

    • comments

      public List<String> comments(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS source)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.comments. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a List<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<List<java.lang.String>> or a Flux<List<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<List<java.lang.String>>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<List<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
      Specified by:
      comments in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the comments attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • booleans

      public List<Boolean> booleans(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS source)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.booleans. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a List<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<List<java.lang.Boolean>> or a Flux<List<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<List<java.lang.Boolean>>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<List<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
      Specified by:
      booleans in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the booleans attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • aliases

      public List<String> aliases(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS source)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.aliases. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a List<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<List<java.lang.String>> or a Flux<List<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<List<java.lang.String>>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<List<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
      Specified by:
      aliases in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the aliases attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • planets

      public List<String> planets(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS source)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.planets. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a List<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<List<java.lang.String>> or a Flux<List<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<List<java.lang.String>>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<List<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
      Specified by:
      planets in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the planets attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • friends

      public STP_HumanConnection_STS friends(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS source)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.friends. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_HumanConnection_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_HumanConnection_STS> or a Flux<org.allGraphQLCases.server.STP_HumanConnection_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_HumanConnection_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_HumanConnection_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:
      friends in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the friends attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • oneWithIdSubType

      public CompletableFuture<STP_AllFieldCasesWithIdSubtype_STS> oneWithIdSubType(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_AllFieldCasesWithIdSubtype_STS> dataLoader, SIP_AllFieldCasesInterface_SIS source)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.oneWithIdSubType. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_AllFieldCasesWithIdSubtype_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_AllFieldCasesWithIdSubtype_STS> or a Flux<org.allGraphQLCases.server.STP_AllFieldCasesWithIdSubtype_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_AllFieldCasesWithIdSubtype_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_AllFieldCasesWithIdSubtype_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:
      oneWithIdSubType in interface DataFetchersDelegateAllFieldCasesInterface
      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
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the oneWithIdSubType attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.

    • listWithIdSubTypes

      public List<STP_AllFieldCasesWithIdSubtype_STS> listWithIdSubTypes(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS source, Integer nbItems, Boolean uppercaseName, String textToAppendToTheForname)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.listWithIdSubTypes. 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_AllFieldCasesWithIdSubtype_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_AllFieldCasesWithIdSubtype_STS>> or a Flux<List<org.allGraphQLCases.server.STP_AllFieldCasesWithIdSubtype_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_AllFieldCasesWithIdSubtype_STS>>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<List<org.allGraphQLCases.server.STP_AllFieldCasesWithIdSubtype_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:
      listWithIdSubTypes in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the listWithIdSubTypes attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      nbItems - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      uppercaseName - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      textToAppendToTheForname - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.

    • oneWithoutIdSubType

      public STP_AllFieldCasesWithoutIdSubtype_STS oneWithoutIdSubType(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS source, SINP_FieldParameterInput_SINS input)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.oneWithoutIdSubType. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_AllFieldCasesWithoutIdSubtype_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_AllFieldCasesWithoutIdSubtype_STS> or a Flux<org.allGraphQLCases.server.STP_AllFieldCasesWithoutIdSubtype_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_AllFieldCasesWithoutIdSubtype_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_AllFieldCasesWithoutIdSubtype_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:
      oneWithoutIdSubType in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the oneWithoutIdSubType attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      input - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.

    • listWithoutIdSubTypes

      public List<STP_AllFieldCasesWithoutIdSubtype_STS> listWithoutIdSubTypes(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS source, Integer nbItems, SINP_FieldParameterInput_SINS input, String textToAppendToTheForname)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads the data for AllFieldCasesInterface.listWithoutIdSubTypes. 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_AllFieldCasesWithoutIdSubtype_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_AllFieldCasesWithoutIdSubtype_STS>> or a Flux<List<org.allGraphQLCases.server.STP_AllFieldCasesWithoutIdSubtype_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_AllFieldCasesWithoutIdSubtype_STS>>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<List<org.allGraphQLCases.server.STP_AllFieldCasesWithoutIdSubtype_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:
      listWithoutIdSubTypes in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      source - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the listWithoutIdSubTypes attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      nbItems - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      input - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      textToAppendToTheForname - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.

    • batchLoader

      public List<SIP_AllFieldCasesInterface_SIS> batchLoader(List<UUID> keys, org.dataloader.BatchLoaderEnvironment environment)
      Description copied from interface: DataFetchersDelegateAllFieldCasesInterface
      This method loads a list of ${dataFetcher.field.name}, based on the list of id to be fetched. This method is used by graphql-java java-dataloader to highly optimize the number of requests to the server, when recursing down through the object associations.
      You can find more information on this page: graphql-java batching
      Important notes:
      • The list returned by this method must be sorted in the exact same order as the given keys list. If values are missing (no value for a given key), then the returned list must contain a null value at this key's position.
      • One of batchLoader or unorderedReturnBatchLoader must be overriden in the data fetcher implementation. If not, then a NullPointerException will be thrown at runtime, with a proper error message.
      • If your data storage implementation makes it complex to return values in the same order as the keys list, then it's easier to override unorderedReturnBatchLoader, and let the default implementation of batchLoader order the values
      Specified by:
      batchLoader in interface DataFetchersDelegateAllFieldCasesInterface
      Parameters:
      keys - A list of ID's id, for which the matching objects must be returned
      environment - The Data Loader environment
      Returns:
      A list of IDs

    • forname

      public String forname(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, SIP_AllFieldCasesInterface_SIS origin, Boolean uppercase, String textToAppendToTheForname)
      Custom field data fetchers are available since release 2.5
      Specified by:
      forname in interface DataFetchersDelegateAllFieldCasesInterface
      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 forname attribute of the origin, which is an instance of {InterfaceType {name:AllFieldCasesInterface, fields:{Field{name:id, type:ID!, params:[]},Field{name:name, type:String!, params:[]},Field{name:forname, type:String, params:[uppercase:Boolean,textToAppendToTheForname:String]},Field{name:age, type:Long!, params:[]},Field{name:nbComments, type:Int, params:[]},Field{name:comments, type:[String], params:[]},Field{name:booleans, type:[Boolean!], params:[]},Field{name:aliases, type:[String]!, params:[]},Field{name:planets, type:[String!]!, params:[]},Field{name:friends, type:HumanConnection, params:[]},Field{name:oneWithIdSubType, type:AllFieldCasesWithIdSubtype, params:[]},Field{name:listWithIdSubTypes, type:[AllFieldCasesWithIdSubtype], params:[nbItems:Int!,uppercaseName:Boolean,textToAppendToTheForname:String]},Field{name:oneWithoutIdSubType, type:AllFieldCasesWithoutIdSubtype, params:[input:FieldParameterInput]},Field{name:listWithoutIdSubTypes, type:[AllFieldCasesWithoutIdSubtype], params:[nbItems:Int!,input:FieldParameterInput,textToAppendToTheForname:String]},Field{name:extendedField, type:String, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      uppercase - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      textToAppendToTheForname - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.