Fork me on GitHub
#rum
<
2018-07-11
>
jimmy15:07:33

@souenzzo how about using graphql?

mattly16:07:16

graphql is probably very close to what you want

souenzzo18:07:54

Yeah, it's almost graphql but without a new language. I expect something that allow to declare a query on the view and compose queries as I compose the views. Normalization also good.

James Conkling18:07:31

[qlkit](https://github.com/forward-blockchain/qlkit) also sounds like it might fit the use case. I don’t see explicit bindings for Rum, but it looks un-opinionated enough that it should be relatively straightforward.

James Conkling18:07:08

RE: graphql, are there any well-supported cljs graphql client libraries w/ bindings for rum?

mattly19:07:19

my question there is, how are you managing your state?

mattly19:07:40

you can ask "are there graphql bindings for react?" and the answer is the same thing

mattly19:07:18

graphql is pretty straightforward to consume

mattly19:07:40

it's when you start getting into subscriptions, or partial updates of your local state or whatnot, that you start running into thorny problems

mattly19:07:09

and those are all adjacent to the problem rum solves, which is representing data as views

James Conkling19:07:43

yeah, what I’ve been hoping to find is a cljs graphql client library w/ bindings for Rum, similar to the js Apollo or Relay bindings for React

mattly19:07:06

I'm not entirely sure those even exist for re-frame 😛

James Conkling19:07:27

yeah, I haven’t seen anything for graphql that looks particularly promising. qlkit seems to be taking a stab in that direction, ditto fulcro, om-next, and possibly Reagent/Posh/Datascript and ReFrame/Re-Posh/Datascript

mattly19:07:46

rum is pretty hands-off as far as state management goes, especially compared to om or reagent

mattly19:07:30

I personally am using #citrus but that again is one step removed from the problem of, how do I ingest data from an http source?