This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-06-21
Channels
- # announcements (3)
- # aws (8)
- # babashka (14)
- # beginners (39)
- # biff (22)
- # cider (5)
- # clj-kondo (1)
- # cljs-dev (12)
- # cljsjs (4)
- # clojure (16)
- # clojure-europe (47)
- # clojure-germany (6)
- # clojure-uk (2)
- # clojurescript (36)
- # core-async (29)
- # cursive (19)
- # datalevin (14)
- # etaoin (10)
- # helix (1)
- # hyperfiddle (6)
- # introduce-yourself (5)
- # kaocha (43)
- # keechma (1)
- # lsp (7)
- # nbb (68)
- # new-channels (1)
- # off-topic (12)
- # pathom (11)
- # quil (14)
- # rdf (3)
- # re-frame (5)
- # reitit (6)
- # shadow-cljs (88)
This seems like it would be a huge upgrade if it does what it says: https://github.com/day8/re-frame/pull/754
That would certainly increase the amount of "easy" but I'm not sure if this is sufficiently "simple". For example, wouldn't this make event handlers non-referentially transparent? At the moment they (should) depend on their co-effects as input but this change would also enable a "side-channel" for additional data. Also, does this (or re-frame in general) guarantee that the db
in the co-effects is the same db
that is used for the subscriptions?
I think it would be even better, if we had a subscription api, where you could supply the db as an argument. But I'm sure there's a million different challenges with that.