Any support for pushNamedAndPopUntil about auto_route_library

[Milad-Akarie]

@natintosh not everything is supported for path navigation because a path can push one or multiple pages.
explain your use-case maybe I can suggest something?

[natintosh]

@natintosh not everything is supported for path navigation because a path can push one or multiple pages. explain your use-case maybe I can suggest something?

Okay so I'm working on a multi-module project with multiple teams working on a different module and each module has it own routes... then in the main app we are appending each module's routes during initialization.

class AppRouter extends RootStackRouter {
  final List<AppRouteInfo> routesInfo;

  AppRouter({this.routesInfo = const []}) : super();

  @override
  Map<String, PageFactory> get pagesMap =>
      routesInfo.fold(<String, PageFactory>{}, (previousValue, element) {
        return {...previousValue, ...element.pagesMap};
      });

  @override
  List<AutoRoute> get routes => routesInfo
      .fold(<AutoRoute>[], (prev, element) => [...prev, ...element.routes]);
}

Due to this, we are mostly using named routing to route between modules and there are some use cases whereby I would need to move on to another module and pop all stack until a page and push

for instance...

    context.router.popUntilRouteWithName(RequirementsRoute.name);
    context.router.push('/settings');

          context.router.popUntil((route) => false);
          context.router.replaceNamed('/dashboard');

[Milad-Akarie]

@natintosh not of that explains the need of using paths instead of route objects?