so I'm starting to incorporate compose into an app...
# compose
s
so I'm starting to incorporate compose into an app, and I'm working on setting up navigation with compose and the rest of the app. i have a feature module that I was starting to set up using compose screens. i have a root fragment, that's a wrapper fragment for a composable nav host. The documentation for the compose navigation interoperability says that it's recommended to use wrapper fragments in hybrid apps, but if my module graph is all compose destinations with the exception of the root fragment/entry point, are there going to be any issues that makes doing this not ideal? should I just use fragment wrappers for all the compose screens and not use the composable nav host? navigating to my feature module is no problem, but I haven't gotten into navigating from the feature module to other modules/graphs yet and after re-reading the docs it made me question my approach.