Fork me on GitHub

Having used react-query quite a lot (and actually migrating the old code base to react-query) on a pure JS frontend with a "restish" (i.e. not REST at all) backend, I still would be a bit hesitant to use that with CLJS or graph based APIs, and still more hesitant when combined. I don't think it will be ergonomic, at least if you wouldn't be heavily using the more advanced stuff (time based staleness, automatic refetching, mutations with optimistic local changes). And perhaps only if you would use hooks anyway, and not introduce them to a cljs code base just to make react-query work.


But that is really just my first hunch. If this was relevant to me, I'd probably make some POCs, perhaps make multiple versions of one component to compare.


Appreciate the feedback @tomi.hukkalainen_slac, thanks. I'm gonna try and get a POC of what @wilkerlucio shared above working and see how that goes for now. I'm not familiar with Fulcro though so reading through some of that source and trying to grok what he shared. Definitely prefer a cljs option instead of navigating another big react dependency.

Jakub Holý (HolyJak)18:09:08

I would hope that would be still the most effective way to learn some Fulcro, even though you would only use it for state management via the raw. namespaces.

🙏 2
☝️ 2
Jakub Holý (HolyJak)18:09:19

You want to understand idents, normalization, query and query composition, and load!, I guess