graphql 2020-06-05 | Slack Archive

kaffein14:06:01

hi people!! has anyone here ever played with re-graph please ? I have a little issue while trying to initialize it with re-frame. Even though, I only set the http part of the re-graph init configuration with the following :

cljs.user> (rf/dispatch [::re-graph/init {:http {:url ""} :ws nil}])

when I check re-frame.db/app-db though, I have the following :

cljs.user> db/app-db
#<Atom: {:re-graph {:re-graph.internals/default {:websocket {:url "ws://localhost:8080/graphql-ws", :sub-protocol "graphql-ws", :ready? false, :connection-init-payload {}, :queue [], :reconnect-timeout 5000, :resume-subscriptions? true}, :http-url "/graphql", :http-parameters {}, :subscriptions {}}}}>

oliy17:06:59

Hi, this looks like a bug

oliy17:06:17

Could you try {:ws {:url nil}}

oliy17:06:09

Or actually just leave out the :ws key altogether

oliy17:06:59

So just {:http {:url "..."}}

kaffein14:06:08

is there something I am missing ?

hlship21:06:19

There's new alphas up on Clojars.

hlship21:06:29

Probably turn into full releases next week.

fabrao22:06:55

hello, is there possible to use lacinia with lacinia pedestal as webserver too?

Lennart Buit22:06:55

What do you mean, you can use lacinia-pedestal to make a pedestal service serving a graphql schema handled by lacinia

Lennart Buit22:06:34

There is a little example in lacinia-pedestals readme: https://github.com/walmartlabs/lacinia-pedestal#usage

fabrao00:06:58

No, lacinia-pedestal serving html files

hlship03:06:17

lacinia-pedestal exists to help build routes specific to graphql (and the graphiql ide), but you can also mix in your own routes to handle file downloads, arbitrary stuff (like a /status endpoint), or whatever you need.

fabrao03:06:30

should I see in lacinia part or pedestal do include new routes?

hlship17:06:35

You should read up on Pedestal, it's the general purpose side of this equation, lacinia is the domain-specific part.

2020-06-05

Channels