Package org.allGraphQLCases.server

Class HumanController

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

  • Field Details

  • Constructor Details

    • HumanController

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

  • Method Details

    • name

      @SchemaMapping(field="name") public Object name(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_Human_STS origin, @Argument("uppercase") Boolean uppercase)
      This method loads the data for ${dataFetcher.graphQLType}.name. 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
      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.
      uppercase - 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.

    • bestFriend

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

    • friends

      @SchemaMapping(field="friends") public Object friends(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_Human_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.friends. 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
      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.
      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.

    • comments

      @SchemaMapping(field="comments") public Object comments(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_Human_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.comments. 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
      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.
      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.

    • appearsIn

      @SchemaMapping(field="appearsIn") public Object appearsIn(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_Human_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.appearsIn. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      Note about enumerations: to manage enum values that are java keyword, enum values like if, else (...) are stored in enum values prefixed by _ (like _if, _else...). But this prevents the automatic mapping of spring-graphql to work. So enum values are returned as String by the generated controller.
      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 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.
      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.