public static class SchemaGenerator.Options
extends java.lang.Object
Modifier and Type | Method and Description |
---|---|
SchemaGenerator.Options |
captureAstDefinitions(boolean captureAstDefinitions)
Memory can be saved if the original AST definitions are not associated with the built runtime types.
|
static SchemaGenerator.Options |
defaultOptions() |
boolean |
isCaptureAstDefinitions() |
boolean |
isUseAppliedDirectivesOnly() |
boolean |
isUseCommentsAsDescription() |
SchemaGenerator.Options |
useAppliedDirectivesOnly(boolean useAppliedDirectivesOnly)
The class
GraphQLDirective should really represent the definition of a directive, and not its use on schema elements. |
SchemaGenerator.Options |
useCommentsAsDescriptions(boolean useCommentsAsDescription)
This controls whether # comments can be used as descriptions in the built schema.
|
public boolean isUseCommentsAsDescription()
public boolean isCaptureAstDefinitions()
public boolean isUseAppliedDirectivesOnly()
public static SchemaGenerator.Options defaultOptions()
public SchemaGenerator.Options useCommentsAsDescriptions(boolean useCommentsAsDescription)
useCommentsAsDescription
- the flag to control whether comments can be used as schema element descriptionspublic SchemaGenerator.Options captureAstDefinitions(boolean captureAstDefinitions)
captureAstDefinitions
- the flag on whether to capture AST definitionspublic SchemaGenerator.Options useAppliedDirectivesOnly(boolean useAppliedDirectivesOnly)
GraphQLDirective
should really represent the definition of a directive, and not its use on schema elements.
The new GraphQLAppliedDirective
has been created to fix this however for legacy reasons both classes will be put on schema
elements. This flag allows you to only use GraphQLAppliedDirective
on schema elements.useAppliedDirectivesOnly
- the flag on whether to use GraphQLAppliedDirective
s only on schema elements