Package org.forum.server.graphql.util

Class TopicController

java.lang.Object
org.forum.server.graphql.util.TopicController
@Controller @SchemaMapping(typeName="Topic") public class TopicController extends Object
Author:
generated by graphql-java-generator
See Also:

  • Field Details

  • Constructor Details

    • TopicController

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

  • Method Details

    • author

      @BatchMapping(field="author") public reactor.core.publisher.Flux<Member> author(org.dataloader.BatchLoaderEnvironment batchLoaderEnvironment, graphql.GraphQLContext graphQLContext, List<Topic> keys)
      This methods loads the data for ${dataFetcher.graphQLType}.author. It is generated as the generateBatchMappingDataFetchers plugin parameter is true.
      Parameters:
      batchLoaderEnvironment - The environement for this batch loaded. You can extract the GraphQLContext from this parameter.
      graphQLContext -
      keys - The objects for which the value for the author field must be retrieved.
      Returns:
      This method returns ${dataFetcher.batchMappingReturnType.value}, as defined by the batchMappingDataFetcherReturnType plugin parameter.
      Please look at the spring-graphql annotation for a documentation on how to return the proper values

    • posts

      @SchemaMapping(field="posts") public Object posts(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<Long,Post> dataLoader, Topic origin, @Argument("memberId") Long memberId, @Argument("memberName") String memberName, @Argument("since") Date since)
      This method loads the data for ${dataFetcher.graphQLType}.posts. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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.
      memberId - The parameter that will receive the field argument of the same name for the current data to fetch
      memberName - The parameter that will receive the field argument of the same name for the current data to fetch
      since - The parameter that will receive the field argument of the same name for the current data to fetch
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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.