Releases: tomgilder/routemaster
v0.10.0-dev5
-
Added: length property to PageStack to find out how many pages the stack will generate.
-
Added:
PageStackNavigator.builder
constructor for advanced scenarios to filter which pages are shown in the navigator. -
Fixed: an issue with getting
RouteData.of(context)
in some advanced circumstances. -
Breaking change: renamed and refactored some core Routemaster objects. Unlikely to affect anyone unless you're making custom stateful pages.
v0.10.0-dev4
- Fixes a bug with forward history navigation.
v0.10.0-dev3
Important: this release has some major breaking changes with how Routemaster
interacts with the system back button on Android and web.
-
Minimum supported Flutter version is now 2.5.0.
-
Breaking change: by default, the Android system back button now navigates
backwards chronologically, instead of just popping the navigation stack. -
Breaking change: by default, tabs no longer add an entry to the web history
stack. This means the browser back button will not navigate between tabs.
To use the previous behavior, specifybackBehavior: TabBackBehavior.history
in
the tab page's constructor. -
Added:
history
property onRoutemaster
for chronological history navigation,
for exampleRoutemaster.of(context).history.back()
. -
Added:
popUntil
to pop multiple times with a predicate. -
Fixed: when navigating to a relative route, use the current context's path as
the base, instead of the router's current path.
v0.10.0-dev2
-
Added:
TransitionPage
andTransitionBuilderPage
to make it much easier to customize page push and pop animations. -
Added: private routes - route segments that start with an underscore are not shown to the user. For example
/sign-up/_stepTwo
will be displayed as/sign-up
in the address bar, and the user can not navigate to it by URL.
v0.9.5
v0.9.4
v0.9.3
v0.9.2
v0.9.1
v0.9.0
- Breaking change:
PageStackNavigator
no longer automatically provides aHeroController
- to use heroes, wrap the navigator in aHeroControllerScope
- Breaking change: refactored
PageWrapper
andStatefulPage
(this is unlikely to affect you) - Added a new property to get the current route:
Routemaster.of(context).currentRoute
- Added documentation to all classes, properties and methods
- Fixed:
RouteData.of(context)
sometimes throwing when navigating away from a page - Fixed: issue with rebuilding routes when
RoutemasterDelegate
is recreated