graphql

wilkerlucio 2021-03-16T00:06:40.014700Z

@steveb8n 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

wilkerlucio 2021-03-16T00:07:04.014900Z

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

emccue 2021-03-16T00:08:45.015100Z

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

steveb8n 2021-03-16T00:08:56.015300Z

@wilkerlucio 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

steveb8n 2021-03-16T00:09:41.015500Z

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

emccue 2021-03-16T00:10:16.015700Z

any reason you can't use that?

steveb8n 2021-03-16T00:10:55.015900Z

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

wilkerlucio 2021-03-16T00:11:34.016100Z

@steveb8n 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 🙂

wilkerlucio 2021-03-16T00:12:51.016400Z

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

steveb8n 2021-03-16T00:13:10.016600Z

thanks. I have used om.next 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

steveb8n 2021-03-16T00:14:11.016800Z

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

steveb8n 2021-03-16T00:15:46.017Z

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?

steveb8n 2021-03-16T00:21:01.017200Z

I noticed pathom mentioned here too, hence the question https://book.fulcrologic.com/#_fulcro_and_graphql

steveb8n 2021-03-16T00:22:51.017400Z

I need to read more about Pathom Connect

gklijs 2021-03-16T01:20:18.000100Z

https://github.com/oliyh/re-graph is a nice client, works both on the JVM, and in the browser, not necessarily with re-frame.

steveb8n 2021-03-16T02:38:22.000400Z

@gklijs 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 https://github.com/r0man/grafeo because I prefer it’s terse DSL

wilkerlucio 2021-03-16T03:07:27.001600Z

@steveb8n I suggest you learn strait from Pathom 3 https://pathom3.wsscode.com/, the docs are better there, also better to understand the concepts

steveb8n 2021-03-16T03:07:54.002700Z

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

wilkerlucio 2021-03-16T03:08:05.003300Z

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

steveb8n 2021-03-16T03:08:34.003600Z

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

🙂 1
steveb8n 2021-03-16T03:12:01.003800Z

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