Paweł Gutkowski

That's nice idea, I love the fact that Kotlin is pushing for multiplatform. Most certainly it would take some work, because right now KGraphQL heavily depends on Jackson library for...

It could be useful, but there are lots of great standalone tools for generating documentation from introspection query, so it is nice-to-have, not high priority feature.

Thanks! Unfortunately, KGraphQL does not support other base objects than Query and Mutation. I'm wondering, what's the use case for these?

Hi @StefanHub and @AlphonseSantoro You can use Context in resolvers of queries, extension properties and transformations (I have to update the documentation), see: https://github.com/pgutkowski/KGraphQL/blob/780eda81b740dfe38631a615c1620de7aace05ae/src/test/kotlin/com/github/pgutkowski/kgraphql/schema/SchemaBuilderTest.kt#L321 But if I understand correctly, you...

Hi @Togrias, Thank you for proposal. Standarization of resolver syntax would be nice, although I'm not sold on all potential benefits. Ad1. KGraphQL supports up to 6 arguments, I hope...

Hi @tw, I don't really know what is demand for subscriptions, but I guess it would be really nice addition to KGraphQL. I'm almost sure nobody is working on it,...

Hi @malteseduck, thank you for your report. I'd love to introduce support for object literals, but unfortunately lately I don't have much time due to my career and personal responsibilities....