Aha, looks I need something like this PR to get at the request object: https://github.com/walmartlabs/lacinia-pedestal/pull/41

@timgilbert one way is to send an authentication message down the websocket after it's connected, if it fails I guess you can close the websocket. I think this is how Apollo recommends doing it

However in my web app the user has already authenticated and has a cookie with their token, so it felt like I should be able to accept or deny the websocket connection based on that, hence my PR. Hopefully it will get merged!

@admay @hlship about errors, I've been thinking about using https://github.com/cognitect-labs/anomalies. We currently use equivalent HTTP status codes in the errors array, but agree that's not ideal.

hi @hlship I raised this PR https://github.com/walmartlabs/lacinia-pedestal/pull/42

simple typo, but took me a long time to track down because i couldn't see it either! i thought i was going mad

@timgilbert the other way of doing it is like this (however, this is also not implemented yet) https://github.com/walmartlabs/lacinia-pedestal/issues/25

So, is anyone else running Lacinia in a production app? If so, can you share the details?

Asking for a friend.

Not currently, but we're prototyping a little server to run parallel to our existing app server and serve read-only graphql over our datomic db to an iOS mobile app

We’re almost there, we’re using lacinia in our prototype and when it releases ill give you a ping @hlship!

https://clojurians.slack.com/archives/C073DKH9P/p1512584221000023 might interest some people here niet on the re-frame channel.

Sorry for another pedestal newbie question, but is there a way I can prepend my own interceptor to the front of the queue in lacinia-pedestal? I see the :interceptors param to (service-map), but I'm not sure what values to put in there