This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-16
Channels
- # admin-announcements (5)
- # announcements (2)
- # beginners (2)
- # boot (3)
- # cider (54)
- # clojure (196)
- # clojure-berlin (16)
- # clojure-brasil (4)
- # clojure-dev (36)
- # clojure-italy (3)
- # clojure-japan (9)
- # clojure-korea (3)
- # clojure-russia (18)
- # clojure-uk (24)
- # clojurebridge (11)
- # clojurescript (414)
- # code-reviews (1)
- # core-typed (4)
- # datomic (59)
- # editors (30)
- # euroclojure (2)
- # events (1)
- # jobs (2)
- # ldnclj (16)
- # liberator (11)
- # off-topic (59)
- # om (16)
- # onyx (33)
- # reagent (53)
- # thejaloniki (2)
- # yada (1)
@mattly thanks! I can just use -children
on the parent as well but it seems backwards considering the virtual dom
@mattly how awkward is it? or do you know of another way to access the children of a component through om?
it builds the child components and then you’d just put the :children item from your data/props map into your output somewhere in render
the way most materials for om are written, what becomes this.props
in React is described as data
for om
which when you start getting into cursors makes sense – you’re passing around data that will be rendered
however a lot of the components that I’ve written before have props that are more typically “options”, such as switches for displaying something differently, etc