This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
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
it seems like this is something om leaves as an exercise to the user
I kinda regret going with Om now
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
fwiw, in Om Next if you really want to do component composition that way it will work
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
an alternate pattern is possible via multimethods
this will be my third large React app, first with ClojureScript, and I’ve made extensive use of component composition in the past
yeah I’m reading through some of the issues in the github repo
not saying it’s not a valid complaint, just explaining how it ended up it this way, why it hasn’t changed, and that in the future that pattern will be simple to port if you like :simple_smile:
well, looking forward to it