Oryan

Unfortunately because of the way the scanner works and how different directives are from everything else, this is not a trivial fix.

Here's a working example: ```kotlin class TempTest { @Test fun test() { val schema = SchemaParser.newParser() .resolvers(Query()) .dictionary(Book::class) .dictionary(Author::class) .schemaString( """ union SearchResult = Book | Author type Page {...

This should be partially resolved by #763 for scalars. However, directives with input object arguments/parameters are still not supported (this was the case even before the applied directives change)

@airvine-r7 that fix is merged. You can test it now. #764 is a more complete solution I think should make directives fully supported.

@jamesmartinpp if the problem was with a directive containing an enum parameter it should be fix by https://github.com/graphql-java-kickstart/graphql-java-tools/pull/764 I'm not maintaining older versions so yes, only in 13.1.1.

@crankydillo I don't see what the purpose of a patch would be. The big difference between 13.0 and 13.1 was exactly fixing these issues with directive processing.

@crankydillo Okay I see what you mean. If you want to open a PR for this I can try releasing a "hotfix"

@crankydillo Trying to. The "pipeline" is not built for this.

@crankydillo right so there's a bug in the deploy script that I don't have the time to look into. However, since the artifact was pushed I guess I could create...

@crankydillo Alright I hope this works for you: https://github.com/graphql-java-kickstart/graphql-java-tools/releases/tag/v13.0.4