Is there a way to use KgraphQL in a schema driven way? Most Kotlin graphql tools (this included) seem to focus on a code first approach, and generate the schema from the code. I would like to be able to go the other way, to have a schema defined already, and then handle the resolvers myself. Is that feasible with this library?
Hey 👋
Is there a way to use KgraphQL in a schema driven way? Most Kotlin graphql tools (this included) seem to focus on a code first approach, and generate the schema from the code. I would like to be able to go the other way, to have a schema defined already, and then handle the resolvers myself. Is that feasible with this library?