Question: why are basic react-native components split between many different namespaces?

[markokocic]

Why are components imported from the original "react-native" package split between multiple Clojurescript packages?

It's just me, but I found the old way where you only needed to import steroid.rn.core and have all basic react-native ui components right there instead of requiring multiple packages.

[flexsurfer]

hey, i decided to split because of deprecation of some components in the future https://github.com/flexsurfer/rn-shadow-steroid/issues/3 but probably we could add some components like touchables and list to core, which you would expect to have in core ?

[markokocic]

Intuitively I would expect to follow the react-native packaging convention for the component that are bundled directly with it. Whatever is available after requiring react-native in JavaScript should be available after requiring steroid.rn.core.

That would mean that all the non-deprecated components from react-native will be available in steroid.rn.core, basically all "core components and apis" listed as core in the official docs

I also see you included support for Alert and some other Apis. Following the same logic as for components, they would also belong to steroid.rn.core. On the other hand, maybe it would make sense to have them available in separate steroid.rn.api package.