Expose Lacinia GraphQL as Pedestal endpoints
A library that adds the Pedestal underpinnings needed when exposing Lacinia as an HTTP endpoint.
Lacinia-Pedestal also supports GraphQL subscriptions, using the same protocol as Apollo GraphQL.
Lacinia-Pedestal Manual | API Documentation
For a basic Pedestal server, simply supply a compiled Lacinia schema to the
com.walmartlabs.lacinia.pedestal2/default-servicefunction to generate a service, then invoke
io.pedestal.http/create-serverand
/start.
;; This example is based off of the code generated from the template ;; `lein new pedestal-service graphql-demo`(ns graphql-demo.server (:require [io.pedestal.http :as http] [com.walmartlabs.lacinia.pedestal2 :as lp] [com.walmartlabs.lacinia.schema :as schema]))
(def hello-schema (schema/compile {:queries {:hello ;; String is quoted here; in EDN the quotation is not required {:type 'String :resolve (constantly "world")}}}))
;; Use default options: (def service (lp/default-service hello-schema nil))
;; This is an adapted service map, that can be started and stopped ;; From the REPL you can call server/start and server/stop on this service (defonce runnable-service (http/create-server service))
(defn -main "The entry-point for 'lein run'" [& args] (println "\nCreating your server...") (http/start runnable-service))
Lacinia will handle POST requests at the
/apiendpoint:
$ curl localhost:8888/api -X POST -H "content-type: application/json" -d '{"query": "{ hello }"}' {"data":{"hello":"world"}}
You can also access the GraphQL IDE at
http://localhost:8888/ide.
When developing an application, it is desirable to be able to change the schema without restarting. Lacinia-Pedestal supports this: in the above example, the schema passed to
default-servicecould be a function that returns the compiled schema. It could even be a Var containing the function that returns the compiled schema.
In this way, the Pedestal stack continues to run, but each request rebuilds the compiled schema based on the latest code you've loaded into the REPL.
default-serveris intentionally limited, and exists only to help you get started. Once you start adding anything more complicated, such as authentication, or supporting multiple schemas (or schema versions) at different paths, you will want to simply create your routes and servers in your own code, using the building-blocks provided by
com.walmartlabs.lacinia.pedestal2.
The GraphiQL packaged inside the library is built using
npm, from version
0.12.0.
Copyright © 2017-2020 Walmart
Distributed under the Apache Software License 2.0.
GraphiQL has its own license.