Samuel Vazquez

@jmfayard the idea sound really cool, as currently we only support out of the box auto-configuration for spring server, if we implement a ktor plugin would be super beneficial for...

Hello 👋 , as mentioned on our docs > Given that graphql-java relies on CompletableFutures for scheduling and asynchronous execution of DataLoader calls, currently we don't provide any native support...

regarding the `FederatedTypeResolver`, will check if we can just generalize and change the signature to return a `CompletableFuture` or have a different interface

👋 Thank you very much for your contribution. @WassimAkachi is there any scenario where the current argument deserialization does not work as expected ? while this approach helps to allow...

is there any reason you need to use `ObjectNode` ? why not just create a specify type for `settings` field, which i suspect anyways need a type to do the...

>@samuelAndalon maybe we should encapsulate it in some (open) class so it would be easier to extend? there is definitely room for improvement, the migration from jackson to constructor invocation...

We have added updating to kotlin 1.7.x to the 7.x.x milestone https://github.com/ExpediaGroup/graphql-kotlin/issues/1549 https://github.com/ExpediaGroup/graphql-kotlin/milestone/5 will update documentation of 6.x.x mentioning this specific use case. "custom scalars combined with optional/nullable types on...

https://github.com/ExpediaGroup/graphql-kotlin/pull/1572

Hello, have you looked into https://opensource.expediagroup.com/graphql-kotlin/docs/schema-generator/execution/exceptions/#returning-data-and-errors ? TLDR; you can return `GraphQLError`. also FYI in `7.x.x` we are changing the signature of `FederatedTypeResolver` to return granular elements instead of lists,...

@roookeee created (#1568), will be included in next major release (we still have some tasks in the milestone). what you would need to do is to just throw an exception...