Package org.allGraphQLCases.server

Class AllFieldCasesInterfaceTypeController

java.lang.Object
org.allGraphQLCases.server.AllFieldCasesInterfaceTypeController
@Controller @SchemaMapping(typeName="AllFieldCasesInterfaceType") public class AllFieldCasesInterfaceTypeController extends Object
Author:
generated by graphql-java-generator
See Also:

  • Field Details

  • Constructor Details

    • AllFieldCasesInterfaceTypeController

      public AllFieldCasesInterfaceTypeController(org.springframework.graphql.execution.BatchLoaderRegistry registry)

  • Method Details

    • forname

      @SchemaMapping(field="forname") public Object forname(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin, @Argument("uppercase") Boolean uppercase, @Argument("textToAppendToTheForname") String textToAppendToTheForname)
      This method loads the data for ${dataFetcher.graphQLType}.forname.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • comments

      @SchemaMapping(field="comments") public Object comments(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.comments.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • booleans

      @SchemaMapping(field="booleans") public Object booleans(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.booleans.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • aliases

      @SchemaMapping(field="aliases") public Object aliases(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.aliases.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • planets

      @SchemaMapping(field="planets") public Object planets(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.planets.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • friends

      @SchemaMapping(field="friends") public Object friends(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.friends.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • oneWithIdSubType

      @SchemaMapping(field="oneWithIdSubType") public Object oneWithIdSubType(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_AllFieldCasesWithIdSubtype_STS> dataLoader, STP_AllFieldCasesInterfaceType_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.oneWithIdSubType.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • listWithIdSubTypes

      @SchemaMapping(field="listWithIdSubTypes") public Object listWithIdSubTypes(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin, @Argument("nbItems") Integer nbItems, @Argument("uppercaseName") Boolean uppercaseName, @Argument("textToAppendToTheForname") String textToAppendToTheForname)
      This method loads the data for ${dataFetcher.graphQLType}.listWithIdSubTypes.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • oneWithoutIdSubType

      @SchemaMapping(field="oneWithoutIdSubType") public Object oneWithoutIdSubType(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin, @Argument("input") SINP_FieldParameterInput_SINS input)
      This method loads the data for ${dataFetcher.graphQLType}.oneWithoutIdSubType.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.

    • listWithoutIdSubTypes

      @SchemaMapping(field="listWithoutIdSubTypes") public Object listWithoutIdSubTypes(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCasesInterfaceType_STS origin, @Argument("nbItems") Integer nbItems, @Argument("input") SINP_FieldParameterInput_SINS input, @Argument("textToAppendToTheForname") String textToAppendToTheForname)
      This method loads the data for ${dataFetcher.graphQLType}.listWithoutIdSubTypes.
      For optimization, this method returns a CompletableFuture. 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.
      You can implements this method like the sample below: 
       @Override
 public CompletableFuture<List> friends(DataFetchingEnvironment environment,
                DataLoader<Long, Member> dataLoader, Human origin) {
        List<java.lang.Long> friendIds = origin.getFriendIds();
        DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character");
        return dataLoader.loadMany(friendIds);
 }

      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      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.