Class HumanController
java.lang.Object
org.junittest.customtemplates_server_springconfiguration.HumanController
- Author:
- generated by graphql-java-generator
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected DataFetchersDelegateHuman
protected com.graphql_java_generator.server.util.GraphqlServerUtils
-
Constructor Summary
ConstructorsConstructorDescriptionHumanController
(org.springframework.graphql.execution.BatchLoaderRegistry registry) -
Method Summary
Modifier and TypeMethodDescriptionThis method loads the data for ${dataFetcher.graphQLType}.appearsIn.bestFriend
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID, Character> dataLoader, Human origin) This method loads the data for ${dataFetcher.graphQLType}.bestFriend.This method loads the data for ${dataFetcher.graphQLType}.comments.This method loads the data for ${dataFetcher.graphQLType}.friends.
-
Field Details
-
dataFetchersDelegateHuman
-
graphqlServerUtils
@Autowired protected com.graphql_java_generator.server.util.GraphqlServerUtils graphqlServerUtils
-
-
Constructor Details
-
HumanController
public HumanController(org.springframework.graphql.execution.BatchLoaderRegistry registry)
-
-
Method Details
-
bestFriend
@SchemaMapping(field="bestFriend") public Object bestFriend(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID, Character> dataLoader, Human 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 GraphQLDataFetchingEnvironment
. It gives you access to the full GraphQL context for this DataFetcherdataLoader
- TheDataLoader
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-dataloaderorigin
- 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 aNoSuchElementException
exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use theOptional.get()
method directly, without caring of whether or not there is a value. The generated code will take care of theNoSuchElementException
exception.
-
friends
@SchemaMapping(field="friends") public Object friends(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, Human 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 GraphQLDataFetchingEnvironment
. It gives you access to the full GraphQL context for this DataFetcherorigin
- 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 aNoSuchElementException
exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use theOptional.get()
method directly, without caring of whether or not there is a value. The generated code will take care of theNoSuchElementException
exception.
-
comments
@SchemaMapping(field="comments") public Object comments(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, Human 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 GraphQLDataFetchingEnvironment
. It gives you access to the full GraphQL context for this DataFetcherorigin
- 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 aNoSuchElementException
exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use theOptional.get()
method directly, without caring of whether or not there is a value. The generated code will take care of theNoSuchElementException
exception.
-
appearsIn
@SchemaMapping(field="appearsIn") public Object appearsIn(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, Human 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 GraphQLDataFetchingEnvironment
. It gives you access to the full GraphQL context for this DataFetcherorigin
- 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 aNoSuchElementException
exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use theOptional.get()
method directly, without caring of whether or not there is a value. The generated code will take care of theNoSuchElementException
exception.
-