All Classes and Interfaces
Class
Description
This class is responsible for Publishing new Characters.
This class represents a custom scalar, with all the information to allow proper execution of the generated code
Registry for all
GraphQLScalarType available.This interface contains the fata fetchers that are delegated in the bean that the implementation has to provide, when
fetching fields for the Character GraphQL type, as defined in the provided GraphQL schema.
This interface contains the fata fetchers that are delegated in the bean that the implementation has to provide, when
fetching fields for the Droid GraphQL type, as defined in the provided GraphQL schema.
This interface contains the fata fetchers that are delegated in the bean that the implementation has to provide, when
fetching fields for the Human GraphQL type, as defined in the provided GraphQL schema.
This interface contains the fata fetchers that are delegated in the bean that the implementation has to provide, when
fetching fields for the MutationType GraphQL type, as defined in the provided GraphQL schema.
This interface contains the fata fetchers that are delegated in the bean that the implementation has to provide, when
fetching fields for the QueryType GraphQL type, as defined in the provided GraphQL schema.
This registry logs each DataFetchersDelegate spring component.
This interface contains the fata fetchers that are delegated in the bean that the implementation has to provide, when
fetching fields for the SubscriptionType GraphQL type, as defined in the provided GraphQL schema.
The Builder that helps building instance of this POJO.
Repository is commented: so it's no more found by Spring
TODO remove if really useless
TODO remove if really useless
This annotation contains the information for a directive that was applied to a GraphQL item in the GraphQL schema
used to generate the code.
List of all directives that apply to this GraphQL type, field or parameter
This annotation marks the type, field or method as a non GraphQL one.
This class indicates that this field has at least one input parameter.
This annotation marks all generated classes that are generated to match a GraphQL input type, as defined in the
GraphQL schema.
This annotation marks all fields in the generated classes, that are non scalar.
This Spring autoconfiguration class is used to declare default beans, that can then be overridden, thanks to the
&Primary spring annotation.
This annotation marks all generated classes that are queries/mutations/subscription, as defined in the GraphQL
schema.
This annotation marks all fields in the generated classes, that are standard GraphQL scalar.
A proposed Date scalar, that stores dates in String, formatted as: YYYY-MM-DD
This Scalar is proposed to be used, for integration testing (checks that the plugin correctly manages Custom Scalars, see samples) and with more documentation to help people to create their own Custom Scalar implementations.
This Scalar is proposed to be used, for integration testing (checks that the plugin correctly manages Custom Scalars, see samples) and with more documentation to help people to create their own Custom Scalar implementations.
A proposed DateTime scalar, that stores dates in String, formatted as: 2019-07-03T20:47:55Z
This Scalar is proposed to be used, for integration testing (checks that the plugin correctly manages Custom Scalars, see samples) and with more documentation to help people to create their own Custom Scalar implementations.
This Scalar is proposed to be used, for integration testing (checks that the plugin correctly manages Custom Scalars, see samples) and with more documentation to help people to create their own Custom Scalar implementations.
ID are managed as String, on client side.
ID are managed as UUID, on server side.
Useless String scalar.
It's used both as a sample, to be completed by a developper, according to his/her needs, and for the use in some tests of the plugin logic (like in the Shopify sample, to handle (badly) various scalar as based on strings).
It's actually a bad management, as this custom scalars does nothing, but read basic strings.
It's used both as a sample, to be completed by a developper, according to his/her needs, and for the use in some tests of the plugin logic (like in the Shopify sample, to handle (badly) various scalar as based on strings).
It's actually a bad management, as this custom scalars does nothing, but read basic strings.
A class that contains utility method for the server mode
Thanks to spring-graphql, the POJO classes are auto-magically discovered and mapped.
The Builder that helps building instance of this POJO.
The Builder that helps building instance of this POJO.
Graphql clients can send GET or POST HTTP requests.
The Builder that helps building instance of this POJO.
List of the three GraphQL kind of requests: query, mutation and subscription
The Builder that helps building instance of this POJO.
Various methods used by the velocity templates while generating the code.