Allow sub route path to be absolute path about go_router HOT 4 CLOSED

Hey, @jezsung, thanks for the feedback. Personally, I like my login and signup page to be a single page w/ panels/tabs. However, even if you want them to be separate pages, you can get the behavior you want like so:

GoRouter(routes: [
    GoRoute(path: '/', builder: ...HomePage...),
    GoRoute(path: '/login', builder: ...LoginPage...),
    GoRoute(path: '/signup', builder: ...SignupPage...),
  ],

  error: ...

  redirect: (state) {
    final loggedIn = ...
    final loggingIn = state.subloc == '/login' || state.subloc == '/signup';

    if( !loggedIn && !loggingIn ) return '/login';
    if( loggedIn && loggingIn ) return '/';
    return null;
  },
}

If the user isn't logged in, they'll be sent to /login. If they press Sign Up instead and you send them to '/signup' via context.go('/signup'), that's the link that will show in the address bar. They won't have a Back button on the AppBar but if they press Back on the browser, they'll be redirected to '/login' again, which I think is what you're after.

Does that allow you to do what you want?

from go_router.

@csells This would be ideal for the web, but I want the app bar to have the back button on mobile. This could be achieved by the push function that you mentioned on the other issue. Will that feature be implemented?

from go_router.

@jezsung I think your sign-up page would have a button to login instead, right? I don't think you'd want a Back button on the App bar in this case.

However, yes, I do plan to implement this feature.

from go_router.

dup: #9

from go_router.