This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-29
Channels
- # 100-days-of-code (2)
- # bangalore-clj (1)
- # beginners (141)
- # cider (33)
- # cljs-dev (13)
- # cljsjs (7)
- # cljsrn (1)
- # clojure (88)
- # clojure-conj (3)
- # clojure-dev (24)
- # clojure-italy (11)
- # clojure-nl (4)
- # clojure-russia (1)
- # clojure-sanfrancisco (1)
- # clojure-spec (4)
- # clojure-uk (53)
- # clojurescript (65)
- # core-logic (2)
- # cursive (28)
- # datomic (33)
- # duct (2)
- # emacs (3)
- # figwheel-main (9)
- # fulcro (44)
- # hoplon (6)
- # leiningen (144)
- # mount (1)
- # nrepl (21)
- # off-topic (102)
- # onyx (2)
- # other-languages (5)
- # pathom (6)
- # planck (3)
- # portkey (1)
- # re-frame (7)
- # reagent (5)
- # reitit (17)
- # shadow-cljs (24)
- # spacemacs (16)
- # tools-deps (64)
- # uncomplicate (2)
- # vim (22)
Hey, is there a way to change a variable in a go loop once it's starts running? Trying to change a var in a loop via a subscription but it sticks with the values it was intialized with.
Hi all: what is the best way to schedule a fn to run once after all events have been handled, but before all subscriptions have been synced?
im not sure what all subs have been synced means but maybe you want https://github.com/Day8/re-frame-async-flow-fx
Without more context, you can have 1 event to manipulate whatever data you're transforming dispatching into the fn you want to run as a side effect. And then have that event dispatch into setting your state.
Without more context, you can have 1 event to manipulate whatever data you're transforming dispatching into the fn you want to run as a side effect. And then have that event dispatch into setting your state.
@tavistock, @pcj, thanks for the response! More specifically: the reaction/subscription graph is batch updated via requestAnimationFrame, and I'm wondering if there's a way to hook into that to have a fn run before all the subscriptions are updated. There's next-tick
, which does exactly that, but that is a one time thing. I could just set up recursive call to next-tick
, but haven't seen that as a design pattern anywhere, so I was checking if there's some established way of scheduling something to run regularly.