We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A pattern I've landed on w/ multiple handlers is to have:
(def kit-config {:graphql.kit/engine "..."}) (def http-handler (kit.http/handler kit-config)) (def ws-handler (kit.ws/handler kit-config)) (def graphiql-handler (kit.graphiql/handler {:enabled? true, #_...})
In order to not perform extra work, it'd be good to allow for eager and/or lazy compilation:
(def kit-config (kit.util/precompile {:graphql.kit/engine "..."})) ; or for lazy, but single compilation. Basically would be: `(lazy (kit.util/precompile ...))`. #_(def kit-config (kit.util/lazy-compile {:graphql.kit/engine "..."})) (def http-handler (kit.http/handler kit-config)) (def ws-handler (kit.ws/handler kit-config)) (def graphiql-handler (kit.graphiql/handler {:enabled? true, #_...})
The text was updated successfully, but these errors were encountered:
bnert
No branches or pull requests
A pattern I've landed on w/ multiple handlers is to have:
In order to not perform extra work, it'd be good to allow for eager and/or lazy compilation:
The text was updated successfully, but these errors were encountered: