Closed AAverin closed 2 years ago
Hello @AAverin my first thought would be providing the GuidDate inside of GuidScreen through context using Provider, inherited state or such, so you have access to it anywhere down the widgets tree.
@Milad-Akarie Looks like the only way to go is to make sure routes don't have parameters and share all the data some other way?
Stale issue message
I have this flow
Guide screen loads
guide
inside it and guide is supposed to be shared between all tabs. With Navigator 1.0 what I was doing is just changing the selected page when route was triggered. Now withAutoTabsScaffold
it looks like triggering a new route doesn't just change the page, but also expect all the parameters to be passed to the route.The exact use case is:
What would be a good way to share GuideData between the tabs while still navigating with the Router and deeplinks? Imaginable solution:
/guide/:id/map
should create GuideScreen that will fetch GuideData and create all the subscreens, and final step of the navigation should be just changing selected tab in the bottom navigation.