Hi,

I was browsing the kgraphql.io documentation and i was redirected to your repository. I am in the process of building a saas app using ktor and graphql. Browsing the web for tips and help i came across this old tutorial https://michaelstromer.nyc/books/kotlin-multiplatform-mobile/ktor-and-kgraphql which i followed and made it somehow work with ktor 2 since kgraphql doesnt for now.

I was looking for a better way to handle authentication (with access and refresh tokens) and stumbled upon your repo. If you have a course or tutorial about it please forward it to me so i can improve my current architecture which is mostly organized as shown in the link above. If no videos are available then ill try my best to understand and update where it makes sense.

Thank you for the great repo

@ESchouten I added argument renaming to graphql-kotlin although the way I did it is a little unusual

I worked with the Hook methods didGenerateQueryField and didGenerateMutationField to modify the schema and rename the arguments

Doing this broke the DataFetcher (the original implementation compares the name of the query argument with the name of the function parameter, if there is a match calls the convertArgumentValue for the conversion)... This method convertArgumentValue is internal and not public, so I had to retrieve it with reflections

I honestly don't understand the purpose of the two methods didGenerateQueryField and didGenerateMutationField, because every change in the schema results in a break in the datafetcher

the /login endpoint sends a cookie; this cookie uses the CookieEncoding.URI_ENCODING encoding by default.

before executing the parseAuthorizationHeader method you must decode the cookie, otherwise it will never be recognized as correct

I assume the repo is meant as an example, especially as it is linked here https://kgraphql.io/Examples/. However as long as there is no appropriate licence attached to it, nobody is actually allowed to use this as a starting point for their own project. See https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository#choosing-the-right-license for details.

If this isn't intentional, would you mind adding a licence file?

I noticed that with Ktor 2.0.3 when a query or a mutation trows an error the Graphql server shows the error like this

(example with login query) { "error": "Server response was missing for query 'Login'." }

in Ktor 2.0.1 errors are shown instead like this { "errors": [ { "message": "Invalid authentication", "locations": [ { "line": 2, "column": 3 } ], "path": [] } ] }

is this new behaviour correct or stills a parsing error with this new Ktor version?

ps: also tried with the new version of KGrapgql 0.17.15

Like GraphQL, Rest APIs with OpenAPI generated docs, can enable client-side code generation

Third-party alternative

Since we're only utilizing GraphQL as a typed API, using GraphQL is overkill and requires a lot of verbose queries on the client-side.

OpenAPI would provide a nice, less verbose alternative to the GraphQL API, while maintaining the ability to generate code on the client-side.

Ktor official OpenAPI support

Planned on the latest roadmap

Greeting, I want to create a new module just like you did in this repo with the adapters, domain and use-cases modules but I don't know how to add the correct type of module with intellij.

With KGraphQL development being stale since august 2021 and the developer going AWOL, other graphql server libraries should be considered.

Update JUNE 2022: KGraphQL author seems to have returned, looking for maintainers

Possible candidates: Kaguya GraphQL Kotlin Possible official KTOR Graphql support post 2.0 release