Fork me on GitHub

@gadfly361 awesome! this is great enough. thanks! 😄


@gadfly361 wow, I actually tried the demo of it and it's really good :thumbsup:


i'm hitting a rather interesting architectural challenge with reagent. is there a way to access state in an ratom without wanting it to perform a re-run of the function (in this case, one that is tracked). For example, I track a function that I want to run when one piece of state changes, but that function, when it runs, also needs access to another piece of state -- but if I access that second item, that will also cause the entire function to run again when that second piece of state changes, even though I only want the function triggered when the first piece changes. In other words, is there a way to simply read the contents of an ratom without the reader getting registered for a re-render/re-track?


However unless you're building a debugging tool, I would think more about how to reformulate the problem


Why do you want to only rerun on the first piece of data change, but not the second?


indeed, it's more of an architectural problem. i think the problem is I'm relying on Reagent for matters that not related to UI specifically, so I'll refactor that out separately.


i was using app state sort of like a message channel to avoid circular dependencies which can quite easily happen. in the past i used core.async with great effect for things like this and think i'll head back in that direction


(defn run [] ;;Todo this subscription does not run I have no Idea ;;I expect it to run on every :text sub change (let [ok @(re-frame/subscribe [:text])] (clear) (reagent/render-component (my-eval) (.getElementById js/document "baby-dom-target"))))


can not subscribe :thinking_face: 😳 😰


does it subsrcibe only from hiccup?


@faxa you might try the #re-frame channel instead


that makes sense 😉