IssueTracker

As part of Navigation 2.4.0-alpha04, the navigation-fragment artifact now offers an AbstractListDetailFragment that implements a two pane layout:

• the left (start) list pane is provided by subclasses by overriding onCreateListPaneView()
• the right (end) detail pane is implemented as a NavHostFragment, controllable by overriding onCreateDetailPaneNavHostFragment()

It automatically handles the system back button (i.e., going back from the detail pane to the list pane on phones).

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.