This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-19
Channels
- # aleph (1)
- # announcements (3)
- # aws (1)
- # beginners (95)
- # calva (15)
- # clojars (4)
- # clojure (84)
- # clojure-android (3)
- # clojure-austin (1)
- # clojure-chicago (1)
- # clojure-dev (66)
- # clojure-europe (3)
- # clojure-italy (15)
- # clojure-nl (13)
- # clojure-uk (33)
- # clojuredesign-podcast (9)
- # clojurescript (6)
- # cursive (68)
- # data-science (4)
- # datavis (1)
- # datomic (13)
- # emacs (4)
- # fulcro (2)
- # jobs (4)
- # jobs-discuss (89)
- # luminus (23)
- # nrepl (6)
- # off-topic (2)
- # onyx (2)
- # pathom (4)
- # pedestal (11)
- # re-frame (9)
- # reagent (8)
- # reitit (5)
- # shadow-cljs (131)
- # spacemacs (13)
- # sql (8)
- # vim (8)
- # xtdb (7)
- # yada (4)
How can we dispatch multiple events using something like #(re-frame/dispatch [[...][...]])
Similar to {:dispatch-n [[...] [...]}
effect.
I want to dispatch from UI.
I've found that sometimes dispatching several events from views at once is a smell. I've ended up refactoring such cases to dispatch a single event with a good and describing name and then using dispatch-n
in that events handler if necessary.
i want to have something like a "replayable" interceptor that stores the event to be potentially replayed after an effect. Im confused as to how I can associate the original "replayable" event after a callback from a effect. Do i need to pass additional information to the effect?
what im trying to do is dispatch an event that does a POST to a server from a group (server A and server B). what i would like to do is on certain failures attempt the original event on the other server (if server A fails try server B)