You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if you need a route different from the defaul one (taken from the composable name),@Destination has a parameter you can use to set whatever route you want.
At this point, there's no plan to do something like that. In this case, I would call your composables SignUpTermsOfService and SignInTermsOfService. Even if they're in different packages, it also would help developers understand where they are at a glance. That or specify a route, although I believe Composable names also need to be unique in current version (that will go away with v2).
Hey,
I have 2 nav-graphs, that are not nested in root navgraph. If I use same name for a destination, I get
com.ramcosta.composedestinations.codegen.commons.IllegalDestinationsSetup: Multiple Destinations with 'terms_of_service' as their route name
.I would expect that destinations are generated based on package name. For example, in case of shared terms of service screen:
That doesn't happen, but instead
com.my.app.destinations.TermsOfServiceDestination
is generated, which I guess is causing the conflict.Am I doing something wrong here?
The text was updated successfully, but these errors were encountered: