Andrei Shikov

Hey, not exactly sure what you are trying to achieve, but I don't think it is possible to use this version in common sourceset with JB or official compose.

@drieks If we are able to convert this AST to PSI, we could replace default KotlinParserDefinition with a custom one, extending grammar as we need, but being compatible with the...

Hey, really happy to see someone trying Compose with React Native! Me and @mdvacca did a few related experiments in October last year, and it should be totally possible to...

You might see Fabric related things in the stack traces even on legacy renderer because we adapted most of the Android native components from legacy renderer to work with both...

> Should I avoid investing any effort in using Compose I think not, frankly the opposite :) My comment had more cautionary intention in case you are adopting Fabric right...

Yep, that's the issue we encountered with Fabric as well. I had to commit a few reflection crimes to get around that limitation, but maybe it is possible to just...

If the only problem is the absense of composition context, it should be possible to extract it from parent view/activity context, and the set it similarly to the way you...

Exported our internal proof of concept from October last year: https://github.com/facebook/react-native/pull/32871 It tries to change a `` component to use Compose, supporting a subset of original props and events. All...

@thevoiceless Ah, interesting, I missed the point where they did it lazily, which makes a lot of sense, tbh I guess for me calling the `createAndInstallWindowRecomposer` sounds like a good...

Great investigation! I think you are on the right track for the most of it, but I am not sure if the bug is in Compose view here. > When...