IssueTracker

https://developer.android.com/guide/navigation/design/type-safety

Given this case:

@Serializable
data object MyRoot

@Serializable
data class MyRoute(val id: String)

// inside a function that builds a nested nav graph:
navigation<MyRoot>(
  startDestination = MyRoute::class // ??? this, I am pretty sure, will crash
) {
    composable<MyRoute> {
      MyScreen()
    }
  }
)

The above developer documentation does not mention how to cope with having routes without default args. I believe one should not be forced to create a default arg, because then you could think that the VM's SavedStateHandle would contain that default arg initially, which is an invalid case. You'd never want to initiate a VM with an empty ID, for example.