IssueTracker

Can you explain your use case? These classes should be built inline and passed directly to the composable function.

I was trying to build a Destination class that would be initialised with NamedNavArgument, and then compute the route string / URI in the correct format given the destination arguments.

val mandatoryArgNames = mandatoryArgs.map { it.name } // error: 'name' is private in NamedNavArgument
val optionalArgNames = optionalArgs.map { it.name } // error: 'name' is private in NamedNavArgument

val mandatoryArgString = mandatoryArgNames.joinToString { "/{$it}" }
val optionalArgString = optionalArgNames
        .takeIf { it.isNotEmpty() }
        ?.joinToString(prefix = "?", separator = "&") { "$it={$it}" } ?: ""

val route = baseRoute + mandatoryArgString + optionalArgString

This way my NavGraph can be constructed with a for loop:

 val mainGraph = NavHost(controller, startDestination = Destinations.dayPager.route) {
    for (dest in Destinations.destinations) {
        composable(dest.route, dest.mandatoryArgs + dest.optionalArgs) {
                dest.composableEntryPoint(...)
        }
    }
}

I think it makes sense to expose these as public vals and also make the destructuring methods public.