riverpod icon indicating copy to clipboard operation
riverpod copied to clipboard

A reactive caching and data-binding framework. Riverpod makes working with asynchronous code a breeze.

Results 227 riverpod issues
Sort by recently updated
recently updated
newest added

**Describe what scenario you think is uncovered by the existing examples/articles** I have an InheritedWidget that provides values, a state and a stream. These come from a separate library. Now,...

documentation

## Situation description `.autodispose` provider is being disposed when no more widgets are subscribed to it. Having this kind of widget tree: `MyScaffold` widget at the top with the bottom...

documentation

**Describe what scenario you think is uncovered by the existing examples/articles** I notice in `autoDispose` documentation: >To tell Riverpod to destroy the state of a provider when it is no-longer...

documentation

**Describe what scenario you think is uncovered by the existing examples/articles** I successfully tested my FutureProvider adapting this code from [riverpod.de](https://riverpod.dev/docs/cookbooks/testing#overriding-the-behavior-of-a-provider-during-tests) ``` test('override repositoryProvider', () async { final container =...

documentation

Rather than importing standalone vars with provider names I don't remember, is it ok to use this trick I was previously using with GetIt? ``` // created outside of provider...

documentation

**Describe what scenario you think is uncovered by the existing examples/articles** In the `home.dart` file the `.when` error case doesn't handle DioError, for example doing this: ``` if (err is...

documentation

https://riverpod.dev currently does not mention `context/container.refresh` at all. It would be helpful to have a pull-to-refresh cookbook, showcasing `context.refresh` in use.

documentation

Here are the updates for the codegen

It has been decided to remove `cacheTime` as part of the initial release, as the initial implementation had some issues. This issue is for tracking the re-introduction of `cacheTime`, accompagned...

enhancement

It's a bit weird that AsyncErrors are received as "valid data" in the observer

enhancement
breaking