This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-19
Channels
- # aws (4)
- # aws-lambda (2)
- # beginners (67)
- # boot (38)
- # cider (32)
- # cljs-dev (12)
- # cljsrn (2)
- # clojars (2)
- # clojure (190)
- # clojure-chicago (1)
- # clojure-dusseldorf (2)
- # clojure-germany (1)
- # clojure-greece (3)
- # clojure-italy (5)
- # clojure-russia (6)
- # clojure-spec (47)
- # clojure-uk (10)
- # clojurescript (59)
- # cursive (9)
- # data-science (14)
- # datomic (24)
- # devops (16)
- # emacs (8)
- # fulcro (25)
- # graphql (30)
- # hoplon (123)
- # juxt (15)
- # lambdaisland (2)
- # leiningen (4)
- # luminus (6)
- # lumo (9)
- # off-topic (11)
- # om (7)
- # onyx (8)
- # re-frame (14)
- # reagent (5)
- # ring-swagger (5)
- # shadow-cljs (46)
- # spacemacs (41)
- # specter (8)
- # testing (8)
- # unrepl (31)
- # yada (18)
Hey all, om innards question. When (and where in the source) do the props get stored in component local state? I’m running into what appears to be a competition between data in props and data in state, and the copy in state is winning out, causing a bunch of problems. Basis of my question: om props is running max-keys on basis-t to decide whether to return state or props. https://github.com/omcljs/om/blob/master/src/main/om/next.cljc#L1107
props
in react are passed in from the parent, so they aren’t really “stored” per-se
if om.next does a targeted update to a component, its going to store the new values for the component in state
, otherwise it would need to re-render from a parent
@matthavener I see, that clears some things up. do you know which function does the storing of the new values for targeted updates to the component?
I think its update-props!
it all happens in reconcile!
Awesome, thanks @matthavener!