Uniwind support

[Stanislav1275]

All my view with uniwind collapsed

[mfkrause]

Hey, thanks for opening this issue and sorry it took a while! I took a closer look at Uniwind's internals and am, unfortunately, quite sure it'd be technically impossible or at least very hard to add Uniwind support to Boost. Unlike Nativewind for example, Uniwind does not seem to have an interoperability layer to auto-transform className to style on third-party components. They wrap Text and View in their own wrapper components that do this job. When Boost rewrites Text and View to its own native host components (which happens before Uniwind, due to the way Babel and Metro work together), Uniwind can't do that anymore and all className styles collapse.

So, for now, I've documented this as a known incompatibility and the only solution I can offer right now would be to switch to Nativewind, which is compatible with Boost (with some smaller gotchas).

Open to any PRs or creative ideas for Uniwind support, however. I'll keep this issue open.

[Stanislav1275]

that's work with only text:true

[mfkrause]

Good news: Uniwind support is now being worked on for Boost v2. After taking another, deeper look at this, I've found a way to integrate Boost with Uniwind. While this does require some Uniwind-specific work in Boost, Uniwind is large/popular enough at this point that I think it's worth it to integrate like this.

If you're willing to experiment, Uniwind support has already landed in the v2 branch. Otherwise, Boost v2 should be released sometime next week! (I'll close this issue then.)