IssueTracker

since it is already marked as deprecated, we can probably do it by now.

Re comment#5 - it would allow incrementally moving each screen of your app to Compose, continuing to use Navigation with Fragments until you don't actually have any Fragments left. Once you don't have any fragments left, then and only then would you migrate to Navigation Compose.

We are currently incrementally migrating to compose and we have been creating wrapper fragments for our new compose screens which isn't so bad. But one issue is around dialogs and bottom sheets. They cannot be easily migrated because putting the dialog composables inside a dialog fragment creates two dialog windows (one from compose and one from the fragment). For that reason it would be create if we could add composable destinations along side fragment destinations.

why it is not possible to pass de backStackEntry to the composable function in order to get the some arguments inside the composable function?. This feature is very nice but it solves only a part of the problem, the majority of destinations have arguments being passed down.

Re comment#15 - if you look at the test added in comment#14 where we added LocalFragment, you'll see retrieving arguments is exactly the use case for that API using LocalFragment.current.requireArguments()

Is there a way to make this work with the Safe Args plugin? As soon as I add an action to a composable destination like so:

<composable
  android:id="@+id/home_screen"
  android:name="com.example.HomeScreenKt\$HomeScreen" >
  <action
    android:id="@+id/action_home_screen_to_other_fragment"
    app:destination="@id/other_fragment" />
</composable>

My project build fails on the :app:generateSafeArgs task with the following error:

Can't escape identifier `HomeScreenKt\$HomeScreenDirections` because it contains illegal characters: \

Re comment#17 - please file a new issue to track that issue.