public class AppliedDirectiveArgumentsAreValid extends GraphQLTypeVisitorStub
| Constructor and Description |
|---|
AppliedDirectiveArgumentsAreValid() |
| Modifier and Type | Method and Description |
|---|---|
TraversalControl |
visitGraphQLDirective(GraphQLDirective directive,
TraverserContext<GraphQLSchemaElement> context)
This method will be called twice.
|
visitGraphQLAppliedDirective, visitGraphQLAppliedDirectiveArgument, visitGraphQLArgument, visitGraphQLEnumType, visitGraphQLEnumValueDefinition, visitGraphQLFieldDefinition, visitGraphQLInputObjectField, visitGraphQLInputObjectType, visitGraphQLInterfaceType, visitGraphQLList, visitGraphQLNonNull, visitGraphQLObjectType, visitGraphQLScalarType, visitGraphQLType, visitGraphQLTypeReference, visitGraphQLUnionTypeclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitchangeNode, deleteNode, insertAfter, insertBefore, visitBackRef, visitGraphQLCompositeType, visitGraphQLDirectiveContainer, visitGraphQLFieldsContainer, visitGraphQLInputFieldsContainer, visitGraphQLInputType, visitGraphQLModifiedType, visitGraphQLNullableType, visitGraphQLOutputType, visitGraphQLUnmodifiedTypepublic TraversalControl visitGraphQLDirective(GraphQLDirective directive, TraverserContext<GraphQLSchemaElement> context)
GraphQLTypeVisitorTraverserContext.getParentNode() will be the schema element that this is applied to.
The graphql-java code base is trying to slowly move away from using GraphQLDirectives when they really should be GraphQLAppliedDirectives
and this is another place that has been left in. In the future this behavior will change and this will only visit directive definitions of a schema, not where
they are applied.visitGraphQLDirective in interface GraphQLTypeVisitorvisitGraphQLDirective in class GraphQLTypeVisitorStubdirective - the directivecontext - the traversal context