This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-01-04
Channels
- # announcements (1)
- # babashka (1)
- # beginners (84)
- # biff (22)
- # calva (9)
- # cider (8)
- # clerk (5)
- # clj-kondo (10)
- # clojure (105)
- # clojure-europe (13)
- # clojure-nl (1)
- # clojure-norway (44)
- # clojure-spec (4)
- # clojure-uk (6)
- # clojuredesign-podcast (36)
- # cursive (13)
- # datomic (24)
- # dev-tooling (8)
- # emacs (8)
- # hyperfiddle (4)
- # jobs (1)
- # leiningen (2)
- # london-clojurians (1)
- # lsp (5)
- # malli (6)
- # membrane (11)
- # nyc (1)
- # off-topic (14)
- # other-languages (8)
- # pathom (25)
- # pedestal (2)
- # re-frame (4)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (98)
- # sql (5)
- # squint (1)
- # tools-deps (38)
- # vim (8)
- # xtdb (11)
I am wondering if it considered "bad practice" or a "code smell", when having an event that dispatches another event?
As long as you do it via :dispatch
or some other effect and not via rf/dispatch
or some other function, it's alright.
One common misconception that I would like to clarify is that subs and events are not functions, even though they may look like them. This misunderstanding sometimes makes you want to fire event from another event. I’m not sure about current version, but in older versions this might’ve introduce slight delays between events. But if it’s not the case and you sure, then it’s alright, like @U2FRKM4TW said.
👍 1