shpasha

My current workaround is: - Pass navigator to NavigatorDisposer class, which inherits ScreenDisposable - When Screen is disposed NavigatorDisposer also disposes navigator Sample code: ``` private class NavigatorDisposer : ScreenDisposable...

> What would the `disposeNavigator` function be in your workaround? @shpasha @hristogochev you can find `disposeNavigator` function implementation in [voyager source codes](https://github.com/adrielcafe/voyager/blob/f7c11580039bfb57e6a3bdf9b3ab4c0ea8d21441/voyager-navigator/src/commonMain/kotlin/cafe/adriel/voyager/navigator/internal/NavigatorDisposable.kt#L76)

I suppose that in this case if you navigate from `Screen C` immediately back to `Screen A` your ViewModels inside `Tab A` and `Tab B` will not be cleared I...

Have you tried setting `disposeNestedNavigators = false` in the root navigator?

Also we can get rid of StepDisposableEffect. And emit transition finished events also in CurrentScreen method: ``` @Composable public fun CurrentScreen() { val navigator = LocalNavigator.currentOrThrow val currentScreen = navigator.lastItem...

@DevSrSouza If there are no more problems, maybe we can merge the request?

@DevSrSouza docs updated

Have you tried to implement ScreenTransition like in the sample? This code works fine for me on Android https://github.com/adrielcafe/voyager/tree/main/samples/android/src/main/java/cafe/adriel/voyager/sample/screenTransition