https://phronmophobic.github.io/viscous/ https://github.com/phronmophobic/viscous

Let me know if you run into any issues or have suggestions!

I've been thinking about how to incorporate search, so if you have something in mind, I would be interested to hear your ideas.

@U7RJTCH6J do you support refreshing derefs? For example, Imagine I'm viewing path [:a :d :e :g], and let's say :d is derefable. Am I able to click refresh on :d on that path, and have the data below :d get refreshed?

not currently, but that seems like a good idea

Just created a new issue for it, https://github.com/phronmophobic/viscous/issues/5. It's not that hard to implement, but there are few design decisions: • should values be refreshed on push/pop? • what happens if the current path no longer exists after refreshing? • what happens if the current path throws an exception on refresh? • should there be a way to selectively refresh some atoms and not others? (I'm leaning towards no, but I'm open to being convinced otherwise)

Do you have a more specific description of what you mean for the pattern? Are you referring to the split between cljs and js in the project?

from what i could understand. The components are react components (written in js that must work on their own) and the state-managenment/coordination is done with clojurescript.

Yea, I can't think of anyone open source projects that use that particular pattern. It is not uncommon to have some parts of an app in js and some parts in cljs. Especially if the js part is functional, it can be pretty straightforward.

I dont' believe so. I suggest using shadow-cljs which just uses npm w/ package.json

Trying to find a solution that uses cljsbuild for now, but thanks!