Fork me on GitHub
#graphql
<
2018-03-21
>
eggsyntax13:03:00

I'm not finding anything in the (apparently) latest version of the graphql spec (https://facebook.github.io/graphql/October2016/#index) about subscriptions. Can anyone tell me whether that still exists, or have they replaced it with something else?

gklijs13:03:58

no, they exist, and lacinia supports them

gklijs13:03:36

The graphql spec is very open about them though, I used it with kafka, client could set a filter, and some event would also go to subscribed clients, when they came in.

eggsyntax14:03:35

Cool, thanks!

eggsyntax14:03:56

Mildly annoying that it's not there in the GQL documentation 😜

eggsyntax14:03:18

Just didn't want to start going down that road (w/ lacinia) & then discover the backing functionality was gone 🙂

eggsyntax14:03:39

Really liking lacinia BTW @hlship! If I had to put something on the wishlist (so far), it'd be an extra tutorial that isn't mixed with stuff about lacinia-pedestal, component, etc -- one that presents lacinia just on its own. But that's just a slight wish; the documentation is absolutely great!

hlship15:03:59

There's some unfortunately necessary side tracks, like component and such ... but following the story of this little app will get us to all the interesting edge cases as well. Just a matter of finding the time.

👍 1
eggsyntax15:03:45

I'm working through the tutorial, but I'm integrating lacinia into a project that's luminus-based, and uses mount -- so there's a moderate amount of mental translation happening as I read it 😉

hlship15:03:27

Well, that's the downside of us having choice in the Clojure space. Writing documentation is probably the hardest part of the work, so I'm sticking with what I know and use every day (except for the PostgreSQL stuff, since we mostly use Cassandra internally).

eggsyntax15:03:29

A price I'm definitely willing to pay for choice! That's why I'm suggesting a tutorial that's decomplected from the surrounding tooling -- something that has a section saying, "OK, you need to provide the following as state -- if you're not already using a tool to provide application state (eg component, mount), you should probably read our more comprehensive beginner's tutorial." Note that I'm just trying to clarify my suggestion, not push further for it! I totally get that documentation is hard, and often annoying, and you've done an amazing job with the lacinia documention (definitely better than I usually do 😊 ). Purely a suggestion 🙂

hlship18:03:34

I'm just trusting my intuitions that the documentation will be more readable and useful in a specific context than with tons of hand waving around the context (the context being: component, lacinia-pedestal, etc.).

👍 1
gklijs07:03:11

@hlship thanks for the postgres part in the documentation, was able to replace using an atom for storage to postgres easily, with no prior experience in postgres and little sql. It's a bank emulator, and because of the database, I'm now stuck at 100 transactions/seq.

dominicm14:03:42

are they officially in the spec? I'm not sure they are.

dominicm14:03:57

I think they're a proposal.

eggsyntax14:03:51

This (2015) seems to suggest that they're in the spec: http://graphql.org/blog/subscriptions-in-graphql-and-relay/

eggsyntax14:03:02

"...we’ve introduced a third operation into the GraphQL specification: subscription."

eggsyntax14:03:21

Ah, ok. Thanks!