Replies: 5 comments 6 replies
-
I think the idea would be to have a separate stack for each section? I'm having trouble even wrapping my head around that... |
Beta Was this translation helpful? Give feedback.
-
I think it would be useful to add such functionality to go_router for sure. I'm curious if you try it where go_router falls down and how you think it could be improved. |
Beta Was this translation helpful? Give feedback.
-
There's been a bunch of updates to go_router since this discussion, but I don't see an example that shows using BottomNavigationBar. Is this possible? |
Beta Was this translation helpful? Give feedback.
-
One thing to keep in mind, when using stacked navigation in a bottom navigation bar, as things stand, its very difficult-to-impossible to handle Primary Scroll Controller taps on the status bar. So for iOS apps you lose the coveted tap status bar scroll list view to the top feature when using many stacked navigation arrangements. I'm hoping to start using go_router this weekend and see if it can help in this regard, but incase it doesn't, this is an important thing to consider. |
Beta Was this translation helpful? Give feedback.
-
@csells I think that people want to know how to implement something like this https://youtu.be/9oH42_Axr3Q |
Beta Was this translation helpful? Give feedback.
-
Using Material Design's Bottom Navigation behaviour description I would like to use go_router for "an Android app that requires frequent switching between sections [that] can preserve each section’s state". Would like to be able to use go_router for deep linking and navigation between sections and the creation of individual page stacks where required.
The CupertinoTabView implementation currently uses a Navigator v1 component internally for each bottom navigation item and probably isn't a candidate for use with go_router.
Beta Was this translation helpful? Give feedback.
All reactions