fix schema wiring

[pelletier197]

Resolves #17

As a temporary fix, at least until it is possible to have fields resolved correctly in onField of ValidationSchemaWiring.

This has the downside to only validate the fields directive parameters on the first call to the graphQL API, which is another problem, because the API will start normally and throw an exception on the first call. It's yours to decide if it's better to fail validation at start, but fail to validate half the queries, or throw an exception on the first call...

[bbakerman]

Thanks for this. This is an excellent work around until we can fix upstream.

[bbakerman]

Can I ask that a similar PR get created that targets graphql-java-14-stable branch.

Perhaps @setchy you may be able to help here

[setchy]

Sorted - see #33

[bbakerman]

This is not quite fixed with the PR - that is now if you have self referencing types there is a StackOverflow

input NameRequest {
	         # The title associated to the name
            title: String @Size(min : 1, max : 1)
	        # The given name
	        givenName: String! @Size(min : 1, max : 1)
	        # Middle Name
   	        middleName: String
   	        # Last Name
   	        surName: String!
   	        
   	        # recursion
   	        inner : NameRequest
          }

eg this one. DirectivesAndTypeWalker will stack overflow with such a type because it walks naively

[bbakerman]

See https://github.com/graphql-java/graphql-java-extended-validation/pull/34/files for a fix