Class IFoo1Controller


@Controller @SchemaMapping(typeName="IFoo1") public class IFoo1Controller extends Object
generated by graphql-java-generator
See Also:
  • Field Details

  • Constructor Details

    • IFoo1Controller

      public IFoo1Controller(org.springframework.graphql.execution.BatchLoaderRegistry registry)
  • Method Details

    • bar

      @SchemaMapping(field="bar") public Object bar(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,SIP_IBar1_SIS> dataLoader, SIP_IFoo1_SIS origin)
      This method loads the data for ${dataFetcher.graphQLType}.bar.
      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:
       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);

      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:
      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.
      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.