This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-11-08
Channels
- # announcements (42)
- # aws (2)
- # babashka (69)
- # beginners (38)
- # calva (18)
- # cider (39)
- # circleci (1)
- # clj-commons (10)
- # cljs-dev (2)
- # clojure (36)
- # clojure-australia (14)
- # clojure-europe (25)
- # clojure-gamedev (40)
- # clojure-losangeles (4)
- # clojure-nl (5)
- # clojure-sweden (1)
- # clojure-uk (5)
- # clojurescript (133)
- # core-logic (24)
- # cursive (7)
- # datalevin (4)
- # datascript (3)
- # figwheel-main (1)
- # fulcro (45)
- # honeysql (1)
- # integrant (43)
- # introduce-yourself (1)
- # jobs (4)
- # leiningen (3)
- # lsp (32)
- # nextjournal (9)
- # pathom (18)
- # polylith (21)
- # portal (65)
- # re-frame (6)
- # releases (1)
- # remote-jobs (1)
- # reveal (12)
- # rewrite-clj (1)
- # sci (84)
- # tools-deps (22)
is it ok these days to say @(rf/subscribe [ ...
within the computation-fn of a reg-sub
call? I think I saw a PR or a discussion somewhere saying this is ok now, but perhaps I'm mistaken
It is OK. But just in case - consider if reg-sub-raw
is better suited for your use-case. Especially if @(rf/subscribe ...)
is the return statement or if you don't use either the db
argument or any signal subscription.
Hi! I have a thread where I use map but at the end I need side effects. I'm solving this using doall
, like this: (-> event .-result .-target some-transforms (->> (map more-transformations) (map dispatch-wrapper) doall))
. While this works, it feels wrong. I will dispatch the entire list and handle it in the event handler. Would this be a good solution to realize the seq for side effects once all transformations are in place?
doseq for side effects .. also don't nest -> and ->>, as it becomes hard to read. Do all your transformations first and bind the result to a symbol in a let and then use doseq to run all side effects