Clojurians Log v2
Clojure programming
Channels
Apps
graphql
dominicm 2019-05-08T06:45:32.070800Z
We have talked about it, a lot, but graphql can't express keys that they can, so things get quite complicated.
orestis 2019-05-09T06:40:15.075700Z
What about values? Not having to convert enums, dates etc would be feasible with transit, even with keeping keys as keywords.
dominicm 2019-05-09T07:16:37.075900Z
That's a good point, we never explored that. I think we were focused on namespaced keys :)
donaldball 2019-05-09T14:59:59.079300Z
My primary interest is more efficient serialization, as json is surprisingly often a bottleneck.
dominicm 2019-05-09T16:53:22.092600Z
To generate or decode?
timgilbert 2019-05-14T17:36:07.119100Z
We used transit/json on both sides and then have a kind of net-data-to-domain-objects layer under it that deals with the namespaced keywords and stuff. Much faster than json serialization, but it's a little more code than I'd like
rplevy 2019-05-08T23:32:08.072600Z
is there a parser for graphql syntax that produces expressions in venia (clojure data literal) syntax?
hlship 2019-05-08T23:38:00.073800Z
Lacinia parses GraphQL to a simple intermediate format (see the tests for details) and then transforms that into the executable form using a compiled schema. You may be able to leverage the Lacinia grammar and intermediate format.