This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-27
Channels
- # aleph (2)
- # beginners (19)
- # boot (15)
- # cider (1)
- # cljsrn (1)
- # clojure (68)
- # clojure-austin (12)
- # clojure-dev (2)
- # clojure-france (6)
- # clojure-italy (46)
- # clojure-russia (45)
- # clojure-spec (55)
- # clojure-uk (41)
- # clojurescript (117)
- # component (15)
- # cursive (54)
- # datomic (24)
- # events (2)
- # funcool (1)
- # instaparse (4)
- # klipse (30)
- # lein-figwheel (3)
- # leiningen (4)
- # luminus (4)
- # om (10)
- # onyx (13)
- # parinfer (36)
- # proton (1)
- # reagent (1)
- # ring (2)
- # ring-swagger (1)
- # rum (19)
- # test-check (6)
- # testing (9)
- # untangled (1)
@bbktsk if you add lots of printlns you'll see that updating the points for a user results in a mutate call keyed on that user (which would be as you'd expect). This is then followed by one or two calls to read ~ :list/one and :list/two as required. Something is determining that your updated person is in one or both of those lists and triggering the read.
get-people splices the per-person data into the list. This is then followed by a render at the Person level (I don't see the RootView or ListView being re-rendered. So a second something is presumably taking the data from the read list and feeding it into the Person ~ which I guess is why you don't see your Person query doing anything, get-people ignores it.
I am shooting from the hip a bit. As @dzannotti suggests, I think reading the code is the way to properly figure it out.
any ideas what could be causing No protocol method IIndexer.key->components defined for type null
?
I think this would be the server streaming page on the wiki that's currently "coming soon"
@mjhamrick https://medium.com/adstage-engineering/realtime-apps-with-om-next-and-datomic-470be2c8204b#.kvomemlwm
@jasonjckn thanks, I’m glad you find it useful 🙂