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, visitGraphQLUnionType
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
changeNode, deleteNode, insertAfter, insertBefore, visitBackRef, visitGraphQLCompositeType, visitGraphQLDirectiveContainer, visitGraphQLFieldsContainer, visitGraphQLInputFieldsContainer, visitGraphQLInputType, visitGraphQLModifiedType, visitGraphQLNullableType, visitGraphQLOutputType, visitGraphQLUnmodifiedType
public TraversalControl visitGraphQLDirective(GraphQLDirective directive, TraverserContext<GraphQLSchemaElement> context)
GraphQLTypeVisitor
TraverserContext.getParentNode()
will be the schema element that this is applied to.
The graphql-java code base is trying to slowly move away from using GraphQLDirective
s when they really should be GraphQLAppliedDirective
s
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 GraphQLTypeVisitor
visitGraphQLDirective
in class GraphQLTypeVisitorStub
directive
- the directivecontext
- the traversal context