This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-09
Channels
- # announcements (1)
- # aws-lambda (3)
- # babashka (6)
- # beginners (91)
- # bristol-clojurians (5)
- # calva (25)
- # chlorine-clover (8)
- # cider (6)
- # clj-kondo (13)
- # cljdoc (10)
- # cljsrn (1)
- # clojure (80)
- # clojure-berlin (6)
- # clojure-europe (29)
- # clojure-nl (4)
- # clojure-spec (18)
- # clojure-uk (51)
- # clojurescript (41)
- # conjure (55)
- # cursive (3)
- # datomic (58)
- # emacs (9)
- # events (1)
- # figwheel-main (2)
- # fulcro (29)
- # graphql (12)
- # helix (4)
- # jobs (4)
- # klipse (8)
- # london-clojurians (1)
- # malli (5)
- # off-topic (13)
- # portal (9)
- # re-frame (30)
- # shadow-cljs (44)
- # spacemacs (7)
- # specter (3)
- # sql (11)
- # tools-deps (71)
- # windows (1)
- # xtdb (10)
Could someone point me to an example of using superlifter
with lacinia
but without pedestal
? The lacinia
example on the superlifter
GitHub page assumes the use of pedestal
.
Thanks!
the lacinia namespace only has two things
• an interceptor for starting a superlifter context (and companion fn for getting it back out) - you don't need these
• the ->lacinia-promise
fn which converts a promesa promise into lacinia promise - you will probably still want this
Very cool, thats for sure! What makes it hard (assumption?) to add this with the edn based schema?
Have to be able to stream out the SDL equivalent to the EDN schema, omitting some things (like the defs for the various directives, like \@key). Also, there’s a few issues with the default names Lacinia uses for types containing operations (QueryRoot or Queries vs. Query).
btw; on the omission of the federation specific directives (like you mentioned @key
), that appears to have been taken care of in the apollo gateway: https://github.com/apollographql/apollo-server/pull/4209
Right, that makes sense. Its probably with good reason, but having the schema SDL as a value in the federation schema always struck me as a bit odd
(I expected like a metaschema like __schema
, but oh well. Nothing to do about it)