A way to pass an already generated GraphQLSchema to kitql and ignore modules? #260
frankmayer
started this conversation in
Ideas
Replies: 1 comment 11 replies
-
Thanks for reaching out 👍. It seems like a good use case. I would like to support a variety of ways of working. I have a few questions to understand better:
|
Beta Was this translation helpful? Give feedback.
11 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi @jycouet
I would like to propose some way to pass an already generated GraphQLSchema to kitql and ignore the modules with their typedefs and resolvers.
I am currently researching
Cuddle would automatically create (and also migrate on changes) the needed GraphDB Collections (nodes and edges) and all needed types and resolvers automatically based on the GraphQL SDL.
The only thing that is needed is to inject that cruddl-produced schema into graphql-yoga. I have tested this on a standalone yoga server and it works great, but it would be great if it would optionally be possible with kitql.
This would mean that we need a way to inject that schema into KitQL, so it can then inject that instead of the modules and also not bother with any schema merging of the modules.
Cruddle would be a perfect fit for people wanting to use ArangoDB and have a relatively easy (as also with KitQL) point of entry.
I might grow out of KitQL for this specific project and run a standalone Yoga server in that configuration, but I think it would still be an interesting option for people (and me 😄) to have.
What do you think?
Beta Was this translation helpful? Give feedback.
All reactions