[flutter_adaptive_scaffold] Go router sample for AdaptiveScaffold

[martijn00]

This implements a sample of using GoRouter with AdaptiveScaffold. It also helps testing advanced adaptive scenarios.

List which issues are fixed by this PR. You must list at least one issue.

flutter/flutter#129850

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or this PR is exempt from CHANGELOG changes.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[martijn00]

@chunhtai can you have a look at this one too?

[gspencergoog]

[martijn00]

@Renzo-Olivares can you have a look?

[martijn00]

@hanskokx could you pitch in with your research findings on this sample?

[hanskokx]

From my experience, AdaptiveScaffold works optimally when paired with AdaptiveLayout. However, there is an issue in flutter_adaptive_scaffold version 0.2.x where the leadingExtendedNavRail does not show up (I've been meaning to file a bug on this). Below is the approach I've utilized in production over the last few years:

classMainAppextendsStatelessWidget {
constMainApp({super.key});
@overrideWidgetbuild(BuildContext context) {
returnMaterialApp.router(
routeInformationProvider:AppRouter.router.routeInformationProvider,
routeInformationParser:AppRouter.router.routeInformationParser,
routerDelegate:AppRouter.router.routerDelegate,
),
);
}
}
enumAppRoute {
root("/", isProtected:false),
home("/splash", isProtected:false),
home("/welcome", isProtected:false),
home("/login", isProtected:false),
home("/register", isProtected:false),
home("/home"),
;
finalString path;
finalbool isProtected;
constAppRoute(this.path, {this.isProtected =true});
}
classAppRouter {
staticfinal router =GoRouter(
errorBuilder: (context, state) =>constErrorScreen(),
navigatorKey:GlobalKey<NavigatorState>(debugLabel:"root"),
initialLocation:AppRoute.splash.path,
debugLogDiagnostics: kDebugMode,
redirect: (BuildContext context, GoRouterState state) {
finalbool routeIsProtected =AppRoute.values.any(
(AppRoute route) =>
state.uri.toString().contains(route.path) && route.isProtected,
);
finalbool unauthenticated =AuthenticationService.I.status ==AuthenticationStatus.unauthenticated;
if (unauthenticated && routeIsProtected) {
return state.namedLocation(
AppRoute.welcome.name,
queryParameters:<String, String>{"from": state.uri.toString()},
);
}
returnnull;
},
routes:<RouteBase>[
GoRoute(
path:AppRoute.root.path,
redirect: (_, __) =>AppRoute.home.path,
),
GoRoute(
name:AppRoute.splash.name,
path:AppRoute.splash.path,
pageBuilder: (context, state) =>MaterialPage(
key: state.pageKey,
child:SplashScreen(),
);
),
// * WelcomeGoRoute(
name:AppRoute.welcome.name,
path:AppRoute.welcome.path,
pageBuilder: (context, state) {
returnMaterialPage(
key: state.pageKey,
child:constWelcomeScreen(),
);
},
routes: [
// LoginGoRoute(
name:AppRoute.login.name,
path:AppRoute.login.path,
builder: (context, state) =>LoginScreen();
routes: [
// Forgot passwordGoRoute(
name:AppRoute.forgotPassword.name,
path:AppRoute.forgotPassword.path,
builder: (context, state) =>AppScaffold(
key: state.pageKey,
body:constForgotPasswordScreen(),
);
),
],
),
// RegisterGoRoute(
name:AppRoute.register.name,
path:AppRoute.register.path,
builder: (context, state) =>constRegisterScreen();
),
],
),
StatefulShellRoute.indexedStack(
builder: (context, state, navigationShell) =>AppScaffoldShell(
navigationShell: navigationShell,
),
branches:<StatefulShellBranch>[
// Home branchStatefulShellBranch(
initialLocation:AppRoute.home.path,
navigatorKey:GlobalKey<NavigatorState>(debugLabel:"home"),
routes: [
GoRoute(
name:AppRoute.home.name,
path:AppRoute.home.path,
pageBuilder: (context, state) {
returnNoTransitionPage(
child:AppScaffold(
key: state.pageKey,
body:HomeScreen(
key:GlobalKey(debugLabel:"Home Screen"),
),
),
);
},
),
],
),
],
),
],
);
}
extensionLandscapeExtensiononBuildContext {
boolget isLandscape =>MediaQuery.of(this).orientation ==Orientation.landscape ||
layoutSize !=LayoutSize.small;
LayoutSizeget layoutSize {
if (Breakpoints.large.isActive(this)) {
returnLayoutSize.large;
} elseif (Breakpoints.medium.isActive(this)) {
returnLayoutSize.medium;
} else {
returnLayoutSize.small;
}
}
}
enumLayoutSize { small, medium, large }
classAppScaffoldextendsStatelessWidget {
finalWidget body;
finalWidget? secondaryBody;
constAppScaffold({
requiredthis.body,
Key? key,
this.secondaryBody,
}) :super(key: key ??constValueKey("ScaffoldWithNestedNavigation"));
@overrideWidgetbuild(BuildContext context) {
returnAdaptiveLayout(
internalAnimations:false,
body:SlotLayout(
config:<Breakpoint, SlotLayoutConfig>{
Breakpoints.small:SlotLayout.from(
key:constKey("Body Small"),
builder: (context) {
finalWidget child = secondaryBody ?? body;
return context.isLandscape ?SafeArea(child: child) : child;
},
),
Breakpoints.mediumAndUp:SlotLayout.from(
key:constKey("Body Medium and Up"),
builder: (context) => context.isLandscape ?SafeArea(child: body) : body;
),
},
secondaryBody:SlotLayout(
config:<Breakpoint, SlotLayoutConfig>{
Breakpoints.small:SlotLayout.from(
key:constKey("Body Small"),
builder:null,
),
Breakpoints.mediumAndUp:SlotLayout.from(
key:constKey("Body Medium"),
builder: (context) => secondaryBody,
),
},
),
),
);
}
}
classAppScaffoldShellextendsStatelessWidget {
finalStatefulNavigationShell navigationShell;
constAppScaffoldShell({
requiredthis.navigationShell,
Key? key,
}) :super(key: key ??constValueKey("ScaffoldWithNestedNavigation"));
@overrideWidgetbuild(BuildContext context) {
returnAdaptiveScaffold(
selectedIndex: navigationShell.currentIndex,
onSelectedIndexChange: onNavigationEvent,
destinations: [
NavigationDestination(...),
NavigationDestination(...),
NavigationDestination(...),
],
body: (_) => navigationShell,
);
}
voidonNavigationEvent(int index) {
navigationShell.goBranch(
index,
initialLocation: index == navigationShell.currentIndex,
);
}
}

[martijn00]

Thanks! I'm curious about the leadingExtendedNavRail bug. I'm working on new implementations that would make things easier. Currently the AdaptiveScaffold implementation is way to complicated.

https://docs.google.com/document/d/1DMFfGrHv_V1Je6_wrfyu0iY3ngJgn317OscfNbuRMRA/pub

Let me know if you have feedback on the doc.

[hanskokx]

Thanks! I'm curious about the leadingExtendedNavRail bug.

I've recorded the behavior I'm seeing in 0.1.12 vs 0.2.2. I haven't had time yet to dig into it and figure out what changed and/or what's broken. It's been on my todo list but I'm right at the end of this project and have needed to focus on getting it shipped.

0.1.12.mov

0.2.2.mov

I'm working on new implementations that would make things easier. Currently the AdaptiveScaffold implementation is way to complicated.

Yeah, that would be great! As you can see from the code I provided before, the true implementation requires far more work than is reasonable. (I even cut a bunch out of that example, such as where I'm disabling animations because they look wonky.) A more streamlined approach would be greatly appreciated.

https://docs.google.com/document/d/1DMFfGrHv_V1Je6_wrfyu0iY3ngJgn317OscfNbuRMRA/pub
Let me know if you have feedback on the doc.

It would be beneficial to have a feature that allows users to resize panes, possibly through a drag handle that becomes visible when tapping between panes. Naturally, this feature would be optional.

Adding panes dynamically would be a useful feature. Consider a list within a list scenario: the first pane displays a list of items, and upon selection, a second pane appears, showing further details and another list. Selecting an item from this secondary list could lead to a deeper list in a new pane or reveal more details about the item. By the third level, the initial pane could automatically hide to prevent screen clutter. (Feel free to disregard if this seems far-fetched.)

[martijn00]

@hanskokx I think you are correct this is a bug. Probably in this code:

final bool isHeightActive = isDesktop ||
orientation == Orientation.portrait ||
(orientation == Orientation.landscape && andUp
? isWidthActive || height >= lowerBoundHeight
: height >= lowerBoundHeight && height < upperBoundHeight);

I have to look into that to figure out where it is.

[martijn00]

@hanskokx because the device size is a width of 841 and a height of 668 it can't be active on mediumLarge because the height starts at 900 but cannot be active at medium because the width doesn't match. Therefor it falls back to standard which is not good in this situation.

I'm not sure yet how to handle this, but my feeling is the breakpoint to apply is mediumLarge. This could be done by lowering the height to maybe 480? The specs are just not very clear on this.

[hanskokx]

@martijn00 Do you know what PR/commit the behavior was changed in? That might provide some insights into why the change was made and illuminate a path forward.

[martijn00]

@hanskokx in this pr #7300

[hanskokx]

@hanskokx in this pr #7300

I wonder if you are a prophet 😅. #7300 (comment)
I agree that your work in refactoring into the Breakpoints enum is the best place to start looking. Perhaps we should spin up a new bug ticket and migrate the conversation there, to keep this PR focused on the sample?

[martijn00]

Yeah i agree a new issue is better. I'll look into adding a test for this case.

[martijn00]

@hanskokx Here is a PR for it: #7549

[martijn00]

@gspencergoog can you add: "override: no changelog needed" label.

[chunhtai]

LGTM