Jan Martiska

This seems to be related to the way how graphql-java prints directives - this call: https://github.com/graphql-java/graphql-java/blob/v18.1/src/main/java/graphql/schema/idl/SchemaPrinter.java#L678 is the culprit, I think it should have been a plain `print` instead of...

I've submitted a fix straight to graphql-java: https://github.com/graphql-java/graphql-java/pull/2920 Let's see if it gets accepted. I've also prepared a test that we will add on our side once we upgrade to...

Fix merged into graphql-java, so this will be resolved on our side with an upgrade to graphql-java 20, when it's released

TBH this sounds like a bit too much of "magic" to me, and there will be edge cases where this will become confusing or hard to implement reasonably. Like @t1...

> Move core package and Request & Response classes to dynamic. These are the MicroProfile APIs that are temporarily copied over from `org.eclipse.microprofile.graphql.client` to `io.smallrye.graphql.client`. The reason I didn't put...

I think that the problem here is that the compiler of Kotlin 1.3 does not store `TYPE_USE` annotations into regular metadata where Java does it, see https://stackoverflow.com/questions/63093833/how-do-i-access-type-use-annotations-in-kotlin-through-reflection , so SmallRye...

Given that Quarkus support for Kotlin 1.4 is in progress (see https://github.com/quarkusio/quarkus/pull/11453) I'd suggest waiting for that, instead of trying to hack it with 1.3

Yeah, the DSL doesn't have that yet. I reported https://github.com/smallrye/smallrye-graphql/issues/871 so we don't forget about it

They can also be used to prevent having to repeat a large chunk of fields several times, like in the example here https://graphql.org/learn/queries/#fragments but this is chiefly a problem when...

I haven't gotten around to it yet. You're welcome to work on it if you wish ;) I think CDI can still remain optional for the client library with this...