This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-16
Channels
- # announcements (7)
- # babashka (1)
- # beginners (25)
- # calva (7)
- # cider (15)
- # clj-kondo (13)
- # cljdoc (14)
- # clojure (151)
- # clojure-europe (4)
- # clojure-hamburg (2)
- # clojure-italy (22)
- # clojure-nl (57)
- # clojure-spec (12)
- # clojure-uk (6)
- # clojuredesign-podcast (5)
- # clojurescript (12)
- # core-async (8)
- # cursive (26)
- # datascript (9)
- # datomic (92)
- # emacs (4)
- # fulcro (7)
- # graalvm (1)
- # graphql (2)
- # instaparse (3)
- # jobs (1)
- # jvm (2)
- # kaocha (6)
- # nrepl (3)
- # off-topic (5)
- # re-frame (45)
- # reagent (5)
- # reitit (18)
- # ring (1)
- # shadow-cljs (89)
- # slack-help (9)
- # spacemacs (2)
- # sql (54)
- # tools-deps (75)
- # vim (28)
- # xtdb (17)
- # yada (31)
@tony.kay I ended up writing the following functions to handle the problem of acting on state changes. I already suspect I’ll have to get rid of it or refactor it later, but it’s alright as an interim solution. https://gist.github.com/eneroth/afe3f0fd9b4cadc1c684e83aec334383
An optimization note: You could use the query (convert it to an AST and use the :component) to pre-pull idents, and then do ref compares on the table contents as a check before db->tree
. Could improve performance.
There’s no guarantee of that. I use it for roughly A -> Bs -> Cs, where both Bs and Cs can come and go.