This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-28
Channels
- # aatree (3)
- # alda (8)
- # avi (21)
- # beginners (37)
- # boot (193)
- # cbus (1)
- # cider (29)
- # cljs-dev (8)
- # cljsjs (3)
- # cljsrn (20)
- # clojure (76)
- # clojure-dev (13)
- # clojure-miami (20)
- # clojure-portugal (2)
- # clojure-russia (220)
- # clojure-sg (2)
- # clojurebridge (5)
- # clojurescript (94)
- # community-development (14)
- # conf-proposals (110)
- # core-async (12)
- # cursive (12)
- # datascript (6)
- # datomic (14)
- # dirac (72)
- # emacs (49)
- # hoplon (86)
- # jobs (33)
- # jobs-discuss (1)
- # ldnclj (6)
- # lein-figwheel (1)
- # off-topic (56)
- # om (139)
- # onyx (29)
- # pedestal (17)
- # proton (23)
- # re-frame (45)
- # reagent (35)
- # ring-swagger (4)
- # test-check (1)
- # testing (8)
- # yada (11)
also just did an app that I might be expanding a bit into some kind of product using om next and datascript.
I love being able to throw the (om/get-query x) straight into datascript pull. But I am displaying dates that are on keys deep in the query. I want to update them so that means re-reading the deep key via core async or so I think.
But since I read the key of the root only I wold need to retrigger the whole query, which is not quite elegant, still thinking about how to solve that. Although this would be a question better asked in #C06DT2YSY
@bbss Hi. Yes. In Shanghai. Not really sure about your issue without seeing code. But if you're updating/mutating a thing in the db the components referencing that part should update automatically. You trigger this by specifying the keys to re-read in the mutate call. Probably more appropriate for #C06DT2YSY.