snapsl

Take a look at the third-party examples [riverpod.dev](https://riverpod.dev/). These show programming patterns that you can follow using riverpod.

I agree that the bloc documentation is more comprehensive and mature than the current state of the riverpod documentation. Also, bloc comes with its own architecture pattern (BLoC). Riverpod, on...

I am kinda curious.. Does this degrade model performance?

Does it help to move onDispose before the async/await part?

Tested and it works. Can this PR be merged so everyone can use this?

@frenck pls, review.

Yes, it will overlap. But, since AsyncValue is exclusiv to riverpod and needed for FutureProvider / AsyncNotifier, a new user has no information about this concept. The documentation could give...

> If we want to improve AsyncValue's docs, I'd rather update the API reference to have better docs. Then link the AsyncValue's dartdoc page better in the doc. Maybe it...

Of course, using riverpod for DI is just a part of it [link](https://riverpod.dev/docs/concepts/providers#why-use-providers). And eventually we use the same concepts (provider, override, testing) that are already defined in the documentation....

That's alright. Is there a certain reason why riverpod should not be used for DI (anymore)? Because I have seen many projects that use riverpod this way and articles that...