This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-01
Channels
- # admin-announcements (1)
- # beginners (16)
- # boot (22)
- # cider (96)
- # clojure (146)
- # clojure-dev (5)
- # clojure-germany (7)
- # clojure-greece (3)
- # clojure-italy (5)
- # clojure-japan (76)
- # clojure-russia (6)
- # clojure-seattle (1)
- # clojure-sg (1)
- # clojure-uk (19)
- # clojure-ukraine (1)
- # clojurescript (114)
- # code-reviews (11)
- # datomic (42)
- # editors (4)
- # euroclojure (3)
- # jobs (18)
- # ldnclj (59)
- # off-topic (1)
- # om (17)
- # reagent (5)
- # yada (43)
I’m coming from extensive work in React to Om, and wondering how one is supposed to hand children to components in om/build
and then how you’d go about getting the equivalent of this.props.children
in the rendered component
mattly: while Om exposes most of React features, it really has more radical philosophy than React
was never a huge fan of higher order component pattern due to weird semantics wrt component local state
but from what I can tell it hasn’t really impeded sophisticated Om programs in any whatsoever and not an often requested thing.
maybe I’ll study some of the larger open-source apps some more to see how they’re handling these patterns