Package org.allGraphQLCases.server
Class AllFieldCasesController
java.lang.Object
org.allGraphQLCases.server.AllFieldCasesController
@Controller
@SchemaMapping(typeName="AllFieldCases")
public class AllFieldCasesController
extends Object
- Author:
- generated by graphql-java-generator
- See Also:
-
Field Summary
Modifier and TypeFieldDescriptionprotected DataFetchersDelegateAllFieldCases
protected GraphqlServerUtils
-
Constructor Summary
ConstructorDescriptionAllFieldCasesController
(org.springframework.graphql.execution.BatchLoaderRegistry registry) -
Method Summary
Modifier and TypeMethodDescription_break
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, String _if) This method loads the data for ${dataFetcher.graphQLType}.break.age
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, String unit) This method loads the data for ${dataFetcher.graphQLType}.age.aliases
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.aliases.booleans
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.booleans.comments
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.comments.dates
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.dates.forname
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, Boolean uppercase, String textToAppendToTheForname) This method loads the data for ${dataFetcher.graphQLType}.forname.friends
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.friends.issue65
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, List<SINP_FieldParameterInput_SINS> inputs) This method loads the data for ${dataFetcher.graphQLType}.issue65.issue66
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID, STP_AllFieldCases_STS> dataLoader, STP_AllFieldCases_STS origin, List<SINP_AllFieldCasesInput_SINS> input) This method loads the data for ${dataFetcher.graphQLType}.issue66.listWithIdSubTypes
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID, STP_AllFieldCasesWithIdSubtype_STS> dataLoader, STP_AllFieldCases_STS origin, Long nbItems, Date date, List<Date> dates, Boolean uppercaseName, String textToAppendToTheForname) This method loads the data for ${dataFetcher.graphQLType}.listWithIdSubTypes.listWithoutIdSubTypes
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, Long nbItems, SINP_FieldParameterInput_SINS input, String textToAppendToTheForname) This method loads the data for ${dataFetcher.graphQLType}.listWithoutIdSubTypes.matrix
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.matrix.oneWithIdSubType
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID, STP_AllFieldCasesWithIdSubtype_STS> dataLoader, STP_AllFieldCases_STS origin, Boolean uppercase) This method loads the data for ${dataFetcher.graphQLType}.oneWithIdSubType.oneWithoutIdSubType
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, SINP_FieldParameterInput_SINS input) This method loads the data for ${dataFetcher.graphQLType}.oneWithoutIdSubType.planets
(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.planets.
-
Field Details
-
dataFetchersDelegateAllFieldCases
-
graphqlServerUtils
-
-
Constructor Details
-
AllFieldCasesController
public AllFieldCasesController(org.springframework.graphql.execution.BatchLoaderRegistry registry)
-
-
Method Details
-
forname
@SchemaMapping(field="forname") public Object forname(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, @Argument("uppercase") Boolean uppercase, @Argument("textToAppendToTheForname") String textToAppendToTheForname) This method loads the data for ${dataFetcher.graphQLType}.forname.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
_break
@SchemaMapping(field="break") public Object _break(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, @Argument("if") String _if) This method loads the data for ${dataFetcher.graphQLType}.break.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
age
@SchemaMapping(field="age") public Object age(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, @Argument("unit") String unit) This method loads the data for ${dataFetcher.graphQLType}.age.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
dates
@SchemaMapping(field="dates") public Object dates(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.dates.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.comments.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
booleans
@SchemaMapping(field="booleans") public Object booleans(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.booleans.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
aliases
@SchemaMapping(field="aliases") public Object aliases(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.aliases.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
planets
@SchemaMapping(field="planets") public Object planets(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.planets.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.friends.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
matrix
@SchemaMapping(field="matrix") public Object matrix(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin) This method loads the data for ${dataFetcher.graphQLType}.matrix.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
oneWithIdSubType
@SchemaMapping(field="oneWithIdSubType") public Object oneWithIdSubType(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID, STP_AllFieldCasesWithIdSubtype_STS> dataLoader, STP_AllFieldCases_STS origin, @Argument("uppercase") Boolean uppercase) This method loads the data for ${dataFetcher.graphQLType}.oneWithIdSubType.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
listWithIdSubTypes
@SchemaMapping(field="listWithIdSubTypes") public Object listWithIdSubTypes(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID, STP_AllFieldCasesWithIdSubtype_STS> dataLoader, STP_AllFieldCases_STS origin, @Argument("nbItems") Long nbItems, @Argument("date") Date date, @Argument("dates") List<Date> dates, @Argument("uppercaseName") Boolean uppercaseName, @Argument("textToAppendToTheForname") String textToAppendToTheForname) This method loads the data for ${dataFetcher.graphQLType}.listWithIdSubTypes.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
oneWithoutIdSubType
@SchemaMapping(field="oneWithoutIdSubType") public Object oneWithoutIdSubType(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, @Argument("input") SINP_FieldParameterInput_SINS input) This method loads the data for ${dataFetcher.graphQLType}.oneWithoutIdSubType.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
listWithoutIdSubTypes
@SchemaMapping(field="listWithoutIdSubTypes") public Object listWithoutIdSubTypes(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, @Argument("nbItems") Long nbItems, @Argument("input") SINP_FieldParameterInput_SINS input, @Argument("textToAppendToTheForname") String textToAppendToTheForname) This method loads the data for ${dataFetcher.graphQLType}.listWithoutIdSubTypes.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
issue65
@SchemaMapping(field="issue65") public Object issue65(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, STP_AllFieldCases_STS origin, @Argument("inputs") List<SINP_FieldParameterInput_SINS> inputs) This method loads the data for ${dataFetcher.graphQLType}.issue65.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-
issue66
@SchemaMapping(field="issue66") public Object issue66(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID, STP_AllFieldCases_STS> dataLoader, STP_AllFieldCases_STS origin, @Argument("input") List<SINP_AllFieldCasesInput_SINS> input) This method loads the data for ${dataFetcher.graphQLType}.issue66.
For optimization, this method returns a CompletableFuture. 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.
You can implements this method like the sample below:@Override public CompletableFuture<List
> friends(DataFetchingEnvironment environment, DataLoader<Long, Member> dataLoader, Human origin) { List<java.lang.Long> friendIds = origin.getFriendIds(); DataLoader<java.lang.Long, CharacterImpl> dataLoader = environment.getDataLoader("Character"); return dataLoader.loadMany(friendIds); } - 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.- 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.
-