Clojurians Log v2

We called that pattern the 'pre-resolve' (or 'hoisting') and it got more complicated for us. For example we would first try to check which fields and sub fields were being queried so we could optimise the fetch. And the more your graph diverges from your data source the higher you might have to hoist and the less reusable your code becomes

We call it the "oracular" pattern; you have an Oracle that predicts what is to come in the future.

How about just a non-functional gist to start with? 😉

@hlship Why isn't lacinia-pedestal able to use the same endpoint for both HTTP and WS (https://lacinia-pedestal.readthedocs.io/en/latest/subscriptions.html#endpoint)?

That's a limitation of Pedestal and, I suspect, derives from how Jetty implements web sockets.

I see, thanks