Excellent example! I'm a newbie in Riverpod. Anyone has any idea how to store the user gotten from firebase after authentication such that I can access the user (including user firebase id) within my app? Thanks

I have multiple providers that I need to watch to determine whether redirects are needed (e.g. auth provider, email verification provider, etc.). In that scenario using the new sync example, my screen visibly flashes when rebuilding multiple times. I did read the README section about how most rebuilds aren't what they seem, but it seems the current approach may only be meant for a single provider at a time? When I remove everything but a single auth provider the behavior is as expected and there is no flickering or visible rebuilding. Is there a suggested approach or any examples showing how to watch more than one provider? Should I create a combined provider that has every bit of state/property the router needs for its redirect? Thanks so much for making this repo!

Hi @lucavenir

   ...
    redirect: router._redirect, // All the logic is centralized here
    routes: router._routes,
   ...

How come private variable _redirect and _routes are accessible?

Thanks Jas

Hey thanks for that repo 👍

But a simple question, how can I customize or even disable the route transitions? I did not found any information beside using GoRoute but nothing with GoRouteData.

Hey mate, love the project. It's working flawlessly for my work. I do have one question about it through, and not necessarily a bug report. How does one call the Global Key to navigate?? I'm creating a web app and I want to have simple navigation tabs in the app bar that take the user to the specified page. For example

return AppBar(
   title: TextButton(
     onPressed: isUserSignedIn
         ? () => key.currentState!.pushNamed('/dashboard')
         : () {
             key.currentState!.pushNamed('/preloginhome');
           },
     child: Text(
       'home',

       ),
     ),
   ),

will give me an errorNavigator.onGenerateRoute was null, but the route named "/preloginhome" was referenced. How can we access the routes we put in the routerProvider globally?

Addresses several issues pointed out from the community onto complete_example, such as:

1. Unnecessary starting rebuilds
2. Scalability issues (e.g. "how do I add more listeners?")
3. Exploits code generation extensively
4. Allows for more stable APIs (touching this example will feel less risky
5. Uses a ProviderObserver, which allows for better understanding of the example

Yes, the code is still (loosely) tested.

You'll notice big changes with respect the old example. Furthermore, the new Notifier API is exploited, so at a first glance it seems like I've made a step backwards, but it's actually the other way around.

As soon as you'll try this, you'll feel more "in control" of what's going on. Just try this out and let me know what you think.

Potentially solves #7 and resolves what #5 was trying to solve.

I'm trying to extend your example to support firebase dynamic links, both on the Web as well as in Android. However, I'm struggling to get it working in conjunction with authentication. I tried to implement it as shown in this tutorial which also uses go_router + riverpod to get dynamic links working, but I have only been able to get it working on Android.

On the web - as soon as I implement the providers as shown in your example, whenver I load a link fresh it makes a cold start of the application and ends up redirecting me to my main page (after I briefly see the correct location). Any hints on that?