Package org.forum.server.graphql.util
Class MutationController
java.lang.Object
org.forum.server.graphql.util.MutationController
- Author:
- generated by graphql-java-generator
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected DataFetchersDelegateMutation
protected GraphqlServerUtils
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptioncreateBoard
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, String name, Boolean publiclyAvailable) This method loads the data for ${dataFetcher.graphQLType}.createBoard.createMember
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, MemberInput input) This method loads the data for ${dataFetcher.graphQLType}.createMember.createPost
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, PostInput post) This method loads the data for ${dataFetcher.graphQLType}.createPost.createPosts
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, List<PostInput> spam) This method loads the data for ${dataFetcher.graphQLType}.createPosts.createTopic
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, TopicInput topic) This method loads the data for ${dataFetcher.graphQLType}.createTopic.
-
Field Details
-
dataFetchersDelegateMutation
-
graphqlServerUtils
-
-
Constructor Details
-
MutationController
public MutationController()
-
-
Method Details
-
createBoard
@SchemaMapping(field="createBoard") public Object createBoard(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("name") String name, @Argument("publiclyAvailable") Boolean publiclyAvailable) This method loads the data for ${dataFetcher.graphQLType}.createBoard. 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.name
- The parameter that will receive the field argument of the same name for the current data to fetchpubliclyAvailable
- 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 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.
-
createTopic
@SchemaMapping(field="createTopic") public Object createTopic(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("topic") TopicInput topic) This method loads the data for ${dataFetcher.graphQLType}.createTopic. 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.topic
- 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 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.
-
createPost
@SchemaMapping(field="createPost") public Object createPost(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("post") PostInput post) This method loads the data for ${dataFetcher.graphQLType}.createPost. 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.post
- 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 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.
-
createPosts
@SchemaMapping(field="createPosts") public Object createPosts(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("spam") List<PostInput> spam) This method loads the data for ${dataFetcher.graphQLType}.createPosts. 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.spam
- 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 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.
-
createMember
@SchemaMapping(field="createMember") public Object createMember(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, @Argument("input") MemberInput input) This method loads the data for ${dataFetcher.graphQLType}.createMember. 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.input
- 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 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.
-