Fork me on GitHub
#cljsrn
<
2016-11-24
>
paul-c03:11:52

@tiensonqin thanks! With that workaround, I assume the tradeoff is a larger app package because it will include component for both platforms. Do you know if the RN packager excludes platform-specific files in release packages? I assume it does.

paul-c04:11:49

@savelichalex thanks! how do you pass the platform-specific components down the component tree - props, app-state? I'm using om.next. I think it would work to have the platform-specific entry points put their platform-specific component classes in the app-state for other components to retrieve.

savelichalex07:11:59

@paul-c I'm just use closures) for i.e.:

(defn my-scene [platform-specific-component]
  (fn [props]
    [platform-specific-component props]))
ios.core
(def scene (my-scene ios-component))
that's all)