This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-18
Channels
- # ai (1)
- # beginners (71)
- # boot (15)
- # cider (26)
- # clara (4)
- # cljs-dev (81)
- # cljsrn (26)
- # clojure (393)
- # clojure-berlin (2)
- # clojure-dev (5)
- # clojure-dusseldorf (1)
- # clojure-greece (5)
- # clojure-italy (6)
- # clojure-russia (97)
- # clojure-serbia (11)
- # clojure-sg (2)
- # clojure-spec (14)
- # clojure-uk (66)
- # clojurescript (58)
- # core-async (19)
- # cursive (18)
- # data-science (2)
- # datomic (75)
- # emacs (20)
- # events (5)
- # figwheel (1)
- # graphql (2)
- # hoplon (29)
- # jobs-discuss (3)
- # juxt (6)
- # lein-figwheel (1)
- # london-clojurians (2)
- # lumo (29)
- # mount (9)
- # off-topic (4)
- # om (16)
- # onyx (25)
- # other-languages (2)
- # pedestal (38)
- # protorepl (2)
- # re-frame (20)
- # reagent (9)
- # ring-swagger (6)
- # sql (10)
- # unrepl (3)
- # untangled (19)
- # utah-clojurians (1)
- # videos (2)
- # vim (20)
so I'm slowly slowly figuring out om.next architectural patterns in anger. Would it be fair to call complex (let [...])
manipulations within my components a code smell, and that these will somehow get rolled up into the reconciler's read
functions?
(I'm modelling something where there might be different quantities of the same item; it models uses of a building detail and they may be in different locations but still part of the "bag" of details).
and let's say I'd like to just have a unique-ified list available in the same component as a summary.
I can do this at the component in a let based on the props, but I have this feeling that this is supposed to be shoved into the reconciler/read function.
and let's assume I'm not totally off base on that: I'm having trouble finding good examples of how that sort of read function might get written, where I stuff derived properties into the {:value {:whatever}}
... I guess maybe as a final transform on what came back from the app state read?
eg. {:value (my-transform-to-add-derived-values {:values :from :query-driven :state :read})}
?
Has anyone else noticed a problem with using a root-level property keyword in a follow-on read not triggering a root re-render?
@tony.kay is the data being queried for changed by the mutation?
@currentoor Ah, right. I bet that is it.
@tony.kay that was the issue for me recently đŸ˜„