What would be the best practice for defining multiple required arguments for compose navigation? Let...

# compose

[allan.conda]

What would be the best practice for defining multiple required arguments for compose navigation? Let’s say there’s multiple ids I need to pass. How about something like this?
screenA/itemId/userId/someToken
Or is below better even though the syntax is for optional arguments…
screenA/itemId?userId={userId}&someToken={someToken}

[Ian Lake]

The guide is pretty clear that you should put arguments in the path of the route if they are required and in query parameters if they are optional

[allan.conda]

Yeah, it’s just that I got feedback that it looks weird…

[Ian Lake]

TBH, a userId and a someToken sound like things that should be injected in and controlled centrally, not something you'd pass as arguments at all

[pawegio]

@allan.conda instead of hardcoding the query I extract extension function:

private fun String.withParams(vararg params: String): String =
    "$this?" + params.joinToString("&") { param -> "$param={$param}" }

and I call:
Destinations.ScreenA.withParams(Param.A, Param.B)
to declare the route.