Jossi, is it practical to add support for bottom sheets as start destinations?
I see the issue now that, without being able to pop the stack, dismissing the modal would go nowhere. perhaps the
could accept a fallback route to navigate to, in cases where the bottom sheet is itself at the bottom of the stack?Or, instead, add some behaviour where the bottom sheet can be set as startDestination, with another destination underneath?Reason I ask is, on iOS we have roughly this capability, by opening a bottom-sheet-style modal in a
callback. I’d like to have some similar capability on Android, so that I can open a bottom sheet when an Activity initially starts.
1 year ago
I don't think that makes a ton of sense.
is only aware of entries on its state's back stack, which means there are only entries with BottomSheetNavigator.Destinations on there.
keeps track of the global back stack but the navigator isn't aware of the
. I think it would make more sense to have your Activity (or whatever is under the sheet) as startDestination and then navigate when the Activity starts.
But cc @Ian Lake cause I'd love to hear his thoughts about
destinations as start destinations
1 year ago
Thanks for the feedback. Yeah I’m open to suggestions on how to handle this use case