Michiel Oliemans

@Knguy47 Did you ever find a solution or did you switch package? Seeing the same problem today.

@villerdex Right now it searches for the types starting at the root resolvers. That could be improved by taking the union definition into account as well.

@dhermanson This has the same cause and fix as #282. The PR to fix make that `SchemaGeneratorDirectiveHelper` public so we can use it from another package has been merged, but...

Could you upgrade to version 5.2.3 and see if it is fixed? Sounds like issue #152 caused by reflectasm which was fixed in that version.

Andrew seems to be pretty tied up with other projects atm. Any of you guys up for creating a PR for this one?

@bentatham Documentation needs to be improved. We've just setup a new documentation home to be able to start improving that, but it'll take time. Are you using the latest version?...

Are you able to share this example in a small repo by any chance? Might be a bit easier and quicker if I can take a look at it that...

I'm getting a compiler error due to missing package: ```xml com.github.tibor-kocsis vertx-graphql-utils ${vertx-graphql-utils.version} ``` But perhaps it's not necessary if it can be reproduced by returning an actual `Future` in...

Using `Future` with an actual return value works as well in my case: ```java Future organization(int organizationid) { return CompletableFuture.completedFuture(new Organization()); } ``` I see your using `Single.just` which is...

Thanks I can reproduce it now. Requires some debugging unfortunately to figure out why it fails in this case. Btw, I see you're explicitly removing unwrapping te `Optional` to replace...