Repository navigation
Navigator should support starting with an initial history #4702
Description
Instead of just pushing the initialRoute, we should split it on / and push every step of the route. So if the initialRoute is "/foo/bar/baz", we should first push "/", then "/foo", then "/foo/bar", then "/foo/bar/baz".
cc @devoncarew
Activity
abarth commentedon Mar 14, 2017
Hum... I'm not sure we want to force that sort of structure on route names. You should be able to load an initial history with more than one route pushed, but we should probably do that by taking a list of route names rather than but splitting a single route name on
/.[-]initialRoute should support hierarchy[/-][+]Navigator should support starting with an initial history[/+]abarth commentedon Mar 14, 2017
I think we'll be able to add this feature in a way that doesn't break the API.
kelegorm commentedon Sep 3, 2017
I don't think setting bunch of routes instead one
/foo/bar/bazis a good idea. For example, consider Google Inbox application. I has "Add Reminder" widget which run application in route of adding reminder, and back action leads to close application. And it is a good behaviour.Hixie commentedon Sep 3, 2017
We support this today actually, both ways. If your routes use
/, we push the whole stack, if they use:or some other separator, we only push the one route.kelegorm commentedon Sep 4, 2017
Can we add it (":route" usage) to docs?
Hixie commentedon Sep 5, 2017
Yeah, see #11607 for the bug tracking the documentation efforts around routes.
[fuchsia] Renamed PresentationInfo (flutter#4702)
github-actions commentedon Aug 17, 2021
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.