You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A directive can apply to an input object types (GraphQLInputObjectType). A check makes sure that the current input instance is of type GraphQLInputObjectType before applying the directive.
As SchemaParser.determineType returns either a GraphQlList, a GraphQLNonNull or a GraphQLTypeReference, such a directive will never be applied.
I suppose there is reason for this behavior (I am new to graphql-java), but: could it be changed or could the instance check be performed in another way? I could allow the directive to run against GraphQLTypeReference as a workaround, but that's broader than my original scope (which iis only inputs, no GraphQLEnum, no GraphQLList, etc.).
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
I am using directives from graphql-java-extended-validation.
A directive can apply to an input object types (
GraphQLInputObjectType
). A check makes sure that the current input instance is of typeGraphQLInputObjectType
before applying the directive.As
SchemaParser.determineType
returns either aGraphQlList
, aGraphQLNonNull
or aGraphQLTypeReference
, such a directive will never be applied.I suppose there is reason for this behavior (I am new to graphql-java), but: could it be changed or could the instance check be performed in another way? I could allow the directive to run against
GraphQLTypeReference
as a workaround, but that's broader than my original scope (which iis only inputs, noGraphQLEnum
, noGraphQLList
, etc.).The text was updated successfully, but these errors were encountered: