Do navigation routes have a length limit? seeing some weird behaviour where if my route is over a ce...

# compose

[Jason Ankers]

Do navigation routes have a length limit? seeing some weird behaviour where if my route is over a certain length (i.e. workouts/{id}/edit) it navigates to the next shortest route instead (workouts/{id})

[Ian Lake]

The root issue will be fixed by https://github.com/androidx/androidx/pull/153

[Ian Lake]

But that only is an issue if you have a string ID. If you declare the type of your ID as a long, etc, then it should already work fine

[Ian Lake]

In general, routes must 1) match, then 2) the most matching Args wins, then 3) the first match wins

[Jason Ankers]

Ok cool, yeah our id is a string

[Ian Lake]

Then the workaround is to declare your destination with the edit first