Tim Malseed
03/02/2022, 2:36 PMval selected = currentDestination
?.hierarchy
?.any { it.route == bottomNavItem.destination.route } == true
1. Is the idea that you have to leverage nested graphs in order for this to work?
I’m sure this probably makes sense (because how else does Compose know that a particular destination belongs to the same hierarchy)
So, assuming that is the case
2. If you have a screen that is accessible from two different Bottom Navigation roots.. You’d have to declare that route twice (once in each graph)?
If that’s how it works, cool. Just want to make sure I’m thinking about this the right wayAdrijan Rogan
03/03/2022, 9:54 AMTim Malseed
03/03/2022, 10:26 AMAdrijan Rogan
03/03/2022, 10:28 AMTim Malseed
03/03/2022, 10:30 AMhierarchy
for this purpose, but I guess I don’t have a very good understanding of the compose navigation backstackIan Lake
03/08/2022, 3:49 AMTim Malseed
03/08/2022, 3:51 AM