Repository navigation
Proposal: [go_router_builder] Allow users to specify onExit as optional #183099
Description
Use Case
I'm using go_router_builder and have three routes
HomeRouteData, Details1RouteData, and Details2RouteData, corresponding to HomePage, Details1Page, and Details2Page.
On HomePage, I push Details1Page and wait for a returned result. here
On Details1Page, I push Details2Page and wait for a result. here
On Details2Page, I pop to return to Details1Page. here
At that point, I continue to pop to go back to HomePage from Details1Page, but I can’t. here
After investigating the root cause, I found that the issue is due to the onExit callback always being passed into the GoRoute constructor.
Proposal
Option 1:
Use a variable similar to caseSensitive to determine whether this route implements the onExit callback.
const TypedGoRoute({
required this.path,
this.name,
this.routes = const <TypedRoute<RouteData>>[],
this.caseSensitive = true,
this.overrideOnExit = false,
});Option 2:
Check whether the child route actually overrides the onExit function at the time build_runner runs: go_router_builder
final bool hasOverriddenOnExit = classElement.methods.any(
(method) => method.name == 'onExit',
);
Activity
[-][go_router_builder] Allow users to specify onExit as optional[/-][+]Proposal: [go_router_builder] Allow users to specify onExit as optional[/+][go_router] Allow users to specify onExit as optional (#11150)
[go_router] Allow users to specify onExit as optional (flutter#11150)
flutter-triage-bot commentedon Jul 15, 2026
This issue is assigned to @hantrungkien but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
[go_router_builder] Allow users to specify onExit as optional (#11151)
[go_router_builder] Allow users to specify onExit as optional (flutte…