Class QueryTypeController
java.lang.Object
org.junittest.starwars_server_springconfiguration.QueryTypeController
- Author:
- generated by graphql-java-generator
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected DataFetchersDelegateQueryTypeprotected com.graphql_java_generator.server.util.GraphqlServerUtils -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptioncharacters(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, String episode) This method loads the data for ${dataFetcher.graphQLType}.characters.This method loads the data for ${dataFetcher.graphQLType}.droid.This method loads the data for ${dataFetcher.graphQLType}.hero.This method loads the data for ${dataFetcher.graphQLType}.human.
-
Field Details
-
dataFetchersDelegateQueryType
-
graphqlServerUtils
@Autowired protected com.graphql_java_generator.server.util.GraphqlServerUtils graphqlServerUtils
-
-
Constructor Details
-
QueryTypeController
public QueryTypeController()
-
-
Method Details
-
hero
@SchemaMapping(field="hero") public Object hero(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("episode") String episode) This method loads the data for ${dataFetcher.graphQLType}.hero. 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.episode- 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
@SchemaMappingannotation - Throws:
NoSuchElementException- This method may return aNoSuchElementExceptionexception. 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 theNoSuchElementExceptionexception.
-
characters
@SchemaMapping(field="characters") public Object characters(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("episode") String episode) This method loads the data for ${dataFetcher.graphQLType}.characters. 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.episode- 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
@SchemaMappingannotation - Throws:
NoSuchElementException- This method may return aNoSuchElementExceptionexception. 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 theNoSuchElementExceptionexception.
-
human
@SchemaMapping(field="human") public Object human(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("id") UUID id) This method loads the data for ${dataFetcher.graphQLType}.human. 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.id- 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
@SchemaMappingannotation - Throws:
NoSuchElementException- This method may return aNoSuchElementExceptionexception. 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 theNoSuchElementExceptionexception.
-
droid
@SchemaMapping(field="droid") public Object droid(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("id") UUID id) This method loads the data for ${dataFetcher.graphQLType}.droid. 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.id- 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
@SchemaMappingannotation - Throws:
NoSuchElementException- This method may return aNoSuchElementExceptionexception. 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 theNoSuchElementExceptionexception.
-