Are there debugging aids where updates to part of the state redraw components that shouldn't depend on that part of the state? I'm using (rand-int 10) in places to see when something changes.

@mbertheau: for this reason I had to patch reagent’s render-queue: https://github.com/darwin/plastic/blob/master/cljs/src/main/plastic/reagent/patch.cljs btw. my logs do also benchmarking, which can be handy when your app grows bigger

you might want to do something similar and put your logging here: https://github.com/darwin/plastic/blob/master/cljs/src/main/plastic/reagent/patch.cljs#L33

I created a prerendering library for re-frame: https://carouselapps.com/prerenderer/

Is this group for users or developers of re-frame: https://groups.google.com/forum/#!forum/reframe-project

Well, it is unknown to the developers

it is related to a UK research university, nothing to do with re-frame

is it expected that #108 will get merged, or should i avoid dynamic subscriptions ?

hahaha, ok.

How is (for [example [1 2]] (button-cell example)) different from (map button-cell [1 2])? I'm getting Wrong number of args (1) passed to app.widgets/button-cell for the for variant. It works if I use (for [example [1 2]] [button-cell example]). What am I missing?

@mbertheau: is it about evaluation? The last for returns a sequence of [button-cell..] components. The first for and map return a sequence of the result of calling (button-cell..)

@mbertheau: as colin says this will be something about evaluation (...) vs building hiccup [...]. See. https://github.com/Day8/re-frame/wiki/Using-%5B%5D-instead-of-%28%29

I forgot that map returns a lazy sequence and reagent doesn't materialize it.

Thanks

hmm. i'm finding i want to pass a function in dispatch to do swap! like updates... e.g. (dispatch [:update-group assoc :name @name]) yet i seem to recall this is regarded as non-idiomatic ... what's wrong with doing it ?

@mccraigmccraig: #108 is likely to get merged, though it will be marked as experimental in the beginning. I’m pretty confident in the approach, but there may be something we’ve missed (i.e. memory leaks) which would mean we would need to back it out or find another approach

@mccraigmccraig: we want events to be pure data. re-frame wants there to be "data flowing".

When the events are all data, they can easily be logged, replayed, etc.