initialRoute doesn't work when it has parameters about precompose HOT 2 CLOSED

Yes, the check is not that important, you can just remove it in #62
I was just wondering in what use case you would need an initial route with parameters, since you cannot pass parameters to the initial route.

from precompose.

I was just wondering in what use case you would need an initial route with parameters, since you cannot pass parameters to the initial route.

I use a nested NavHost to support multistacks, and it works well, for some screens I need to pass some arguments to the initial screen in the nested stack, for now I'm using a workaround of defining a dummy screen as the initial screen, then starting a navigation using LaunchedEffect to the actual screen with parameters, so with this fix, I won't need this workaround.

from precompose.