re: What are the cons of GraphQL? VIEW POST

re: Jeezus man chill out. I just checked their deps on npmjs.org. Didn’t know to check peer deps. Nor did I know that apollo shipped their own.

You can do without. The Clojurescript client just sends a string over the wire, and get a Clojure map back.

That’s what I was thinking, but, I guess, Apollo needs some info on the query for it’s caching solution.

That makes sense. The Clojurescript library is more low level. It might be nice to have something similar to Apollo. But I quite like the simplicity of just binding the results of a query to some data in de dB. It's also easy to combine queries and subscriptions that way.

The big draw to Apollo for me is honestly not so much the caching, alththats a big plus, but the fact that GraphQL-codegen can make fully typed Apollo hooks for each GraphQL query or mutation I write.

It’s magical.

Clojurescript isn't typed so that won't work :P. Although you could build something similar using spec. You could even use generative testing out of the box that way for components created that way.

code of conduct - report abuse