I have navigation destination route like `routeX?argA={argA}&ArgB={ArgB}` . When I query the Bac...

# compose

[Karthi]

I have navigation destination route like routeX?argA={argA}&ArgB={ArgB} . When I query the BackStackEntry from NavController, I would like to use navController.getBackStackEntry("`routeX` ") without optional param as optional params can grow in future. But current api fails as it expects optional param as well. Any reason why the route should match optional params on query?

[allan.conda]

The route you’ll get is routeX?argA={argA}&ArgB={ArgB} and no real values. That one is fixed can be declared once and reused.

[allan.conda]

I’m not sure, but two routes with different arguments is probably considered different and unique routes. 🤔

[Karthi]

yes, you are right about routeX?argA={argA}&ArgB={ArgB} , I edited question. But my question, should it still considered as different routes based on optional params