Class DataFetchersDelegateMutationImpl

java.lang.Object
org.forum.server.specific_code.DataFetchersDelegateMutationImpl
All Implemented Interfaces:
DataFetchersDelegateMutation

@Component public class DataFetchersDelegateMutationImpl extends Object implements DataFetchersDelegateMutation
Author:
etienne-sf
  • Field Summary

    Fields
    Modifier and Type
    Field
    Description
    protected static org.slf4j.Logger
    The logger for this class
  • Constructor Summary

    Constructors
    Constructor
    Description
     
  • Method Summary

    Modifier and Type
    Method
    Description
    createBoard(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, String name, Boolean publiclyAvailable)
    This method loads the data for Mutation.createBoard.
    createMember(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, MemberInput input)
    This method loads the data for Mutation.createMember.
    createPost(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, PostInput postParam)
    This method loads the data for Mutation.createPost.
    createPosts(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, List<PostInput> spam)
    This method loads the data for Mutation.createPosts.
    createTopic(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, TopicInput topicInput)
    This method loads the data for Mutation.createTopic.

    Methods inherited from class java.lang.Object

    clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
  • Field Details

    • logger

      protected static org.slf4j.Logger logger
      The logger for this class
  • Constructor Details

    • DataFetchersDelegateMutationImpl

      public DataFetchersDelegateMutationImpl()
  • Method Details

    • createBoard

      public Board createBoard(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, String name, Boolean publiclyAvailable)
      Description copied from interface: DataFetchersDelegateMutation
      This method loads the data for Mutation.createBoard. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.forum.server.graphql.Board)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.forum.server.graphql.Board> or a Flux<org.forum.server.graphql.Board>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.forum.server.graphql.Board>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.forum.server.graphql.Board>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Specified by:
      createBoard in interface DataFetchersDelegateMutation
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      name - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      publiclyAvailable - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
    • createTopic

      public Topic createTopic(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, TopicInput topicInput)
      Description copied from interface: DataFetchersDelegateMutation
      This method loads the data for Mutation.createTopic. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.forum.server.graphql.Topic)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.forum.server.graphql.Topic> or a Flux<org.forum.server.graphql.Topic>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.forum.server.graphql.Topic>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.forum.server.graphql.Topic>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Specified by:
      createTopic in interface DataFetchersDelegateMutation
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      topicInput - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
    • createPost

      public Post createPost(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, PostInput postParam)
      Description copied from interface: DataFetchersDelegateMutation
      This method loads the data for Mutation.createPost. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.forum.server.graphql.Post)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.forum.server.graphql.Post> or a Flux<org.forum.server.graphql.Post>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.forum.server.graphql.Post>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.forum.server.graphql.Post>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Specified by:
      createPost in interface DataFetchersDelegateMutation
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      postParam - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
    • createPosts

      public List<Post> createPosts(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, List<PostInput> spam)
      Description copied from interface: DataFetchersDelegateMutation
      This method loads the data for Mutation.createPosts. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a List<org.forum.server.graphql.Post>)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<List<org.forum.server.graphql.Post>> or a Flux<List<org.forum.server.graphql.Post>>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<List<org.forum.server.graphql.Post>>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<List<org.forum.server.graphql.Post>>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Specified by:
      createPosts in interface DataFetchersDelegateMutation
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      spam - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
    • createMember

      public Member createMember(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, MemberInput input)
      Description copied from interface: DataFetchersDelegateMutation
      This method loads the data for Mutation.createMember. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.forum.server.graphql.Member)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.forum.server.graphql.Member> or a Flux<org.forum.server.graphql.Member>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.forum.server.graphql.Member>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.forum.server.graphql.Member>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Specified by:
      createMember in interface DataFetchersDelegateMutation
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      input - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.