This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-01-30
Channels
- # announcements (14)
- # aws (2)
- # beginners (167)
- # calva (25)
- # cider (124)
- # cljs-dev (2)
- # cljsrn (7)
- # clojars (2)
- # clojure (113)
- # clojure-europe (2)
- # clojure-italy (6)
- # clojure-spec (30)
- # clojure-uk (90)
- # clojurescript (20)
- # code-reviews (16)
- # cursive (28)
- # data-science (2)
- # datomic (89)
- # duct (97)
- # emacs (4)
- # figwheel-main (12)
- # fulcro (37)
- # graphql (3)
- # java (3)
- # jobs (2)
- # juxt (3)
- # kaocha (37)
- # leiningen (2)
- # luminus (2)
- # off-topic (30)
- # onyx (2)
- # pathom (3)
- # qlkit (1)
- # re-frame (7)
- # reagent (2)
- # reitit (62)
- # remote-jobs (9)
- # shadow-cljs (26)
- # tools-deps (19)
- # vim (1)
- # yada (8)
I'm getting computation_fn is null
when trying to deref a subscription even though i called (rf/reg-sub ::kw fn)
and the browser log shows me that a subscription is registered
@jacobhaag17 what @kasuko said is right. Think of events as logical 'business' actions: "Create account", "Log In", "Archive document". They are all about the what, not about the how. Your event handler can then do whatever it needs to action the event, but the view remains ignorant of it. Events, Subscriptions, Views, and app-db structure should all remain mostly separated from each other, with little knowledge of what the others are doing, except through the exposed interfaces
@ag That namespace comes from https://github.com/Day8/re-frame-debux/blob/master/src/day8/re_frame/tracing.cljc. The function tracing code relies on the presence of re-frame-10x to be useful, but 10x doesn't (currently) bundle the tracing lib
So yep, it's still relevant, it's the way you can trace event handler execution
Thanks for the original reponse @kasuko and elaborating on it @danielcompton 🙂