Would be pretty awesome to extend the re-frame tracing to work with this: https://github.com/skellock/reactotron

I opened an issue, so if you think it looks as awesome as I think, go and thumb it up 😉 https://github.com/skellock/reactotron/issues/57

anyone doing polling in re-frame? looking for a good pattern/library to do it with events and core.async

@caio my two cents: in your init handler you setup setTimeout dispatch (and maybe setting state in the db). Or if you use mount you can wrap it in a defstate. I like to handle start and stop through events though...

that’s what i’m going for, but i’m seeing some bad concurrency issues, so i thought it’d be better to stop and ask here if someone solved this already

@caio: what sort of concurrency issues ?

when starting/stopping it with events. two start events happening at the same time, for instance… but that’s probably my fault, as I wanted to keep the timeout channel inside the app-db

@caio: don't put anything which isn't simple data into the app-db - it makes for an easier life in the end. in the past, i've done something like keeping a registry of polling request control-channels somewhere, each associated with a go-block which loops polling with a timeout until it receives a stop message/close on the control channel...

how lots of go-blocks are handled by javascript? afaik, js runs on a single thread, right?

@caio: yes - go blocks are transformed into a state-machine and run fine on a single thread

good to know that, but this way I’ll have to create global vars to store the channels, and that makes me sad 😞

@caio: a single global atom with a map with url-keys and channel-values - not so bad for clojure-land 🙂

it’s introducing a singleton and all its issues into my pretty little functional code (channels will be the singletons). I guess I’ll go “let over lambda” to try and minimize this issue, but I was really hoping that there was a functional way out of this

having an issue in a handler where the ratom I am expecting is cljs.core/PersistentArrayMap so getting Uncaught Error: No protocol method ISwap.-swap! defined for type cljs.core/PersistentArrayMap any Ideas? handler below (re-frame/register-handler :add-to-want-list (fn [db [_ item-js-obj]] (swap! db assoc-in [:want-list] item-js-obj) )) if I provide the following ... it works (swap! re_frame_ui.db.default-db assoc-in [:want-list] item-js-obj) dispatching via an anchor tag

@javazquez: db in handler is not your app-db atom, it is its naked value

you are supposed to return a new value from the handler, re-frame will do the job of swapping in new value

there must be some inconsistancy

because another handler I wrote fails

Error: No protocol method IAssociative.-assoc defined for type reagent.ratom/RAtom: [object Object]

when I don't use swap

btw. handlers are supposed to be pure, if you happend to be calling anything with exclamation mark inside your handler fn, you are doing it wrong, very wrong 🙂

thank you

I would bet you swap!’d some atom into you app-db, and you created this inconsistency yourself, so your situation is app-db: <ratom value:<ratom: some other value>>

I have been bouncing through reagent docs and other docs and must have pulled in the wrong stuff

I bet your are absolutely correct

are you familiar with cljs-devtools?

no

it would be crystal clear, if you logged app-db atom into console

(with cljs-devtools enabled)

ok.. <runs to read up and implement>

have to go, good luck!

@darwin: : Looks my real issue was that I made the default-db a ratom. Once I changed to a map and made handlers pure.. I am making progress. Thanks for the cljs-devtools suggestion. It is really nice!