This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-11-02
Channels
- # announcements (1)
- # babashka (19)
- # beginners (85)
- # calva (1)
- # cider (23)
- # clara (19)
- # clj-kondo (28)
- # clojars (4)
- # clojure (60)
- # clojure-australia (8)
- # clojure-dev (14)
- # clojure-europe (117)
- # clojure-nl (3)
- # clojure-uk (11)
- # clojurescript (68)
- # conjure (2)
- # core-async (39)
- # cryogen (11)
- # cursive (7)
- # data-science (1)
- # datomic (9)
- # emacs (10)
- # etaoin (1)
- # events (1)
- # fulcro (1)
- # helix (10)
- # jobs (4)
- # kaocha (2)
- # keechma (3)
- # leiningen (1)
- # malli (6)
- # pathom (15)
- # pedestal (10)
- # re-frame (5)
- # reitit (1)
- # remote-jobs (1)
- # rum (3)
- # shadow-cljs (18)
- # tools-deps (30)
- # vim (6)
Putting it simply: do you ever use subscriptions to then put something back to the app-db?
IMO you shouldn’t. Subs are “views” above the data. Only event handlers should change the app-db.
No, that is what interceptors are for. See the built-in on-changes
interceptor, for example.
@U08JKUHA9 good tip, thanks a lot! However, this doesn’t use awesome caching things like subs [supposedly] do.
✔️ 3
@U6HHQ05GB Thanks! Yeah, I’m hesitant also, but still – I don’t see negative scenarios yet. Apart from “shooting myself in the foot”. I agree that it’s an anti-pattern, for sure.
👍 3