Or it does not have to be a graph? It can also be ...
# compose-destinationss
Steven Yang
10/10/2024, 6:36 AMOr it does not have to be a graph? It can also be implemented as two routes in two graphs wrapping the same composable component.
What's the best practice when some screens need to be shown in multiple graphs?
r
Rafael Costa
10/10/2024, 9:52 AMOn V2, you can have something like this:
Copy code
@Destination<ProfileSettingsGraph>
@Destination<RootGraph>
@Composable
fun SomeScreen() {}👍 1
Rafael Costa
10/10/2024, 9:53 AMfor example
Rafael Costa
10/10/2024, 9:54 AMIt would generate two Destinations, like
ProfileSettingsSomeScreenDestinationRootSomeScreenDestinationRafael Costa
10/10/2024, 9:54 AMeach belonging to the corresponding graph
Rafael Costa
10/10/2024, 9:56 AMOn V1, you'd need two Composables each annotated with @Destination and with the respective @NavGraph and then both would call the same composable internally.