Vitali Olshevski

Support added in [1.2.0](https://github.com/olshevski/compose-navigation-reimagined/releases/tag/1.2.0).

Yeah, I was thinking about this as well. But I always thought it is a bit weird to access neighbours' ViewModels, but if anyone uses it that way then yeah,...

Yeah, I believe they originally intended for it to be used just with navigation graphs and nested sub-graphs, but no one stops you from using any destination in the backstack...

@equeim I've created a snapshot version with the requested API implementation. There is no documentation yet, but otherwise it should be usable. Can you please check it out and give...

>Though it's a bit strange from library user point of view why there is NavHostScope interface if we already have NavController. NavHostScope is inevitable because NavController is by design should...

Final API is available in [1.2.0](https://github.com/olshevski/compose-navigation-reimagined/releases/tag/1.2.0) NavHostScope is here to stay. It now exposes all the current NavHostEntries in the same order their associated entries appear in the backstack. `findNavHostEntry`...

@hrach Hi, there is no current integration with `ModalBottomSheetLayout` and `BottomSheetScaffold`. And yes, it is actually not that trivial to implement. I'm planning to give it a go in the...

I'm not sure what you mean by "material bottom sheet". They are all material 🙂 If you mean the default `ModalBottomSheetLayout` and `BottomSheetScaffold`, I haven't said I'm against them, they...

But it is the same as using composable Dialogs. It is just a separate window with a compose layout inside. I've used this library in a separate project and find...

`BottomSheetNavHost` is finally implemented as part of `reimagined-material` artifact in version 1.3.0.