Fork me on GitHub

Q: I am looking to implement a client side GQL API. this rules out Lacinia unfortunately. Looking for suggestions/ideas…


I can use interop and but that rules out JVM SSR which would reduce some complexity for me


ideally I’d find a .cljc answer for this


also considering but it doesn’t support graphql resolvers. @U066U8JQJ any chance you plan to add this?


@U0510KXTU not sure what you mean by graphql resolver support, Pathom has a very distinct processing engine, and expectations there needs to be different from GraphQL, so I don't see it


there is GraphQL integration, but its a different thing, for that you need some graphql processor that already works


If its client side and this is something people have done, i'd imagine some JS lib exists


@U066U8JQJ since pathom resolvers are similar to graphql resolvers, I wondered if you had thought about supporting graphql by added a graphql->eql feature. I see you already support eql->graphql - hence the question


@U3JH98J4R yes, the graphql-js lib mentioned above is an example of that


any reason you can't use that?


no reason at all. I just prefer to use a clojure lib instead of interop because it makes testing the full stack much easier


@U0510KXTU GraphQL and EQL have the same goal of shape resolution, but Pathom resolvers are not like GraphQL resolvers, internally they are very different things (very different expectations). GraphQL is completly based (and depends on) a type system, Pathom approach is very different than that, I suggest you try Pathom for a while, and you can feel the difference yourself 🙂


its a design choice for Pathom to not have a upfront schema, and I believe to make something that looks like GraphQL we would need one, and that's a not for Pathom


thanks. I have used previously and I’ve also played with pathom. I like the approach. that’s why I think it would be a great solution to my client side requirement


ah, ok. that clarifies it more. that’s a shame but I can see why you prefer schema-less


in theory, I could create a graphql->eql transform fn, even though the EQL layer doesn’t have a schema? I wonder if this would work?


I noticed pathom mentioned here too, hence the question


I need to read more about Pathom Connect

gklijs01:03:18 is a nice client, works both on the JVM, and in the browser, not necessarily with re-frame.


@U26FJ5FDM thanks but I need a gql server impl to run in the client in this case. I have used re-graph but these days I use because I prefer it’s terse DSL


@U0510KXTU I suggest you learn strait from Pathom 3, the docs are better there, also better to understand the concepts


ok. thanks for the tip. I’ll take a look


even if you use pathom 2 (the current, which is production grade tested, pathom 3 isnt)


I listened to your podcast interview. got me enthused to check it out again 🙂

🙂 3

new docs look great. I like the babashka example. that’s a use-case I hadn’t thought of