Fork me on GitHub
#graphql
<
2022-05-31
>
hlship16:05:02

So, an announcement; I’ve left work at Walmart on May 20th; I’ll be starting at Cognitect on July 5th. I’ve been enjoying some down time, but I haven’t forgotten about Lacinia. Although I’m no longer working for Walmart, it looks like I’ll continue to be the main contributor and community liason, at least for the meantime; any work on Lacinia will continue to carry the Walmart copyright. For the larger community, nothing much should change, Lacinia is largely stable.

👍 21
🤯 1
steveb8n23:05:10

Congrats! Thanks for all you and team have done for us. We’re glad you’ll still be involved. Hope the break treats you well

orestis04:06:43

Thank you for everything and congrats! Perhaps time for us users of Lacinia to also take part in development. I confess I've no clue of Lacinia internals…

gklijs21:06:45

Congrats, surely it will work out fine.

hlship19:06:16

Lacinia’s implementation is complicated in a couple of ways due to a) optimizations and b) async ResolverResult. Perhaps we should never have done async ResolverResult (most people would not have cared) but the optimizations are important, and made more complex by async ResolverResult. It’s mostly about shifting as much processing “forward” to a compile or parse stage rather than constantly making decisions during query execution. So start at the resolve-and-select function and work out from there.

👍 2