This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-23
Channels
- # ai (1)
- # beginners (84)
- # boot (111)
- # cider (2)
- # cljsrn (9)
- # clojure (245)
- # clojure-italy (2)
- # clojure-mke (1)
- # clojure-russia (6)
- # clojure-spec (92)
- # clojure-uk (32)
- # clojurescript (55)
- # core-async (1)
- # cursive (8)
- # datomic (19)
- # events (1)
- # hoplon (379)
- # lambdaisland (4)
- # lein-figwheel (8)
- # off-topic (115)
- # om (18)
- # om-next (5)
- # onyx (25)
- # re-frame (8)
- # reagent (5)
- # ring-swagger (1)
- # rum (19)
- # schema (3)
- # untangled (24)
@vikeri At its core, re-frame is event driven. When an event happens, it is processed by event handlers. Later, there is a reactive process by which the UI is updated. It sounds to me like you want to use the reactive process (subscriptions) to do something imperative? Or maybe a further dispatch. Have I understood?
Are you seeking to know when X happens so you can then do Y. Is it like that?
@mikethompson That is correct! I want to schedule a notification based on the updated reaction. I could add a listener to the re-frame event, but then I’d have to redo all the logic that is now in my subscription handlers, it would be much easier to just monitor my subscriptions with add-watch
. It’s just funny that add-watch
works as intended if I’m also referring to the same subscription in a component.