riverpod
riverpod copied to clipboard
A reactive caching and data-binding framework. Riverpod makes working with asynchronous code a breeze.
The issue for tracking the documentation revamp Feel free to suggest issues that are important. This list of issues is not an exhaustive list (for now) - List all providers...
Linter
Let's add custom lint rules for helping to catch mistakes It can include things such as: - [x] "Avoid using ref.read inside build" - [x] "Do not dynamically create providers"...
I honestly didn't quite understand what we agreed upon ;-) I hope this fits better with your expectations.. When digging through the code it looked to me to be cleaner...
Riverpod version `2.0.0-dev.4` adds a `disposeDelay` feature to all `autoDispose` providers and to `ProviderContainer`/`ProviderScope`. This configures the amount of time before a provider is disposed when it is not listened....
**Is your feature request related to a problem? Please describe.** I have run into a problem recently where if a `FutureProvider` depends on data from other `FutureProvider`s, refreshing the top...
`Unhandled Exception` occurs and autoDispose.family *future* provider stuck in `AsyncLoading` state when app uses `WidgetsFlutterBinding.ensureInitialized()` and `runZonedGuarded()` together. **To Reproduce** sample code ```dart import 'dart:async'; import 'package:flutter/foundation.dart'; import 'package:flutter/material.dart'; import...
Currently if an exception is thrown within a Provider/FutureProvider/... then the exception is never sent to the zone. This is "alright" for a `Provider`, as they rethrow the error on...