Luca Venir

> Hi @lucavenir, this is not right. If you look at the snippet, you will see that I consciously pass a `navigatorKey` to `GoRouter`. This means that the tree will...

@creativecreatorormaybenot Do you mind take a look at [this branch](https://github.com/lucavenir/go_router_riverpod/tree/alternative_approach)? I'm trying your suggestion but I still seeing the "root widget" rebuilding, there.

Thank you @creativecreatorormaybenot for the in-depth explanation!! This is way clearer. I guess I'm still confused by Flutter's `key`s.

Hi @creativecreatorormaybenot ! I've updated the examples in [this repo](https://github.com/lucavenir/go_router_riverpod), thanks to you! I've cited you as a contributor, but I'm unsure on how to give you more credit than...

Hi there, I want to share some thoughts. 1. I feel this example is very much needed. I'm still pretty much proud (😂) of the examples from my repo, but...

@josh-burton There's a good chance that your failing `FutureProvider` _is_ reporting that to your observer, but in its `didUpdateProvider` method. If I may, here's a workaround while we wait for...

Hi @rrousselGit, I'd like to go back at this, one year later. I can see that this issue is often referenced, thus maybe it's worth discussing a potential bug here....

> I assume it's because onDispose is throwing? Yeah, that's what I meant there (I linked the precise line throwing). You can't call `onDispose` _after_ the provider is _already_ disposed....

Okay, that's fine. Can't wait to see Riverpod's future about this 😛

Isn't this solved? As of now I do see `maxWidth` in the APIs.