This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-31
Channels
- # aleph (9)
- # bangalore-clj (1)
- # beginners (115)
- # cider (16)
- # clara (20)
- # cljs-dev (47)
- # cljsrn (50)
- # clojure (70)
- # clojure-dusseldorf (2)
- # clojure-italy (16)
- # clojure-sanfrancisco (1)
- # clojure-spec (9)
- # clojure-uk (37)
- # clojurescript (132)
- # cursive (21)
- # datomic (36)
- # dirac (53)
- # fulcro (34)
- # graphql (6)
- # hoplon (96)
- # jobs (2)
- # juxt (2)
- # keechma (2)
- # leiningen (5)
- # off-topic (3)
- # om (2)
- # om-next (3)
- # parinfer (3)
- # re-frame (17)
- # remote-jobs (1)
- # shadow-cljs (57)
- # specter (12)
- # sql (43)
- # unrepl (11)
- # yada (5)
Hello, could anyone explain the reason for separating computed props (`computed`/`get-computed)` from other props when you pass down props to a child component? What's the reason you shouldn't just e.g. pass down a callback function as a normal prop? I tried just using a normal prop for a callback and it seems to work, but read that it's better to use computed-props.
@pontus.colliander It's explained really well here (Fulcro is an om-next fork, differs a bit but some of the core concepts like computed
are exactly the same) http://book.fulcrologic.com/#_passing_callbacks_and_other_parent_computed_data