I want to show CircularProgressIndicator while waiting for future to resolve using flutter_riverpod, here is my code snippet. But it's not showing, I am using ConsumerStatefulWidget is this right way to do it? ElevatedButton( onPressed: () { rejectResponse = ref…
I thought Riverpod will only trigger rebuild if the state value is different but turn out it rebuild every time when state is set although the value is the same. Is that true? The case is as below @Freezed(genericArgumentFactories: true)…
This is my usecase: data is downloaded final dataProvider = FutureProvider<MyModel>((ref) async { return fetchData(); }); and it's used like this within widget's build method: ref.watch(dataProvider).when( data: DataWidget(data), error: ErrorWidget(), loading: LoadingWidget()) user has option to refresh the data: ref.refresh(dataProvider.future);…
I use Riverpod as state management in my web app. I am trying to build an AppBar that scrolls automatically to certain parts of a ListView. I created a ScrollController as a provider for this purpose. final scrollControllerProvider = StateProvider<ScrollController?>((ref)…
I get the warning "Do not use BuildContext across async gaps" when I use code like this: await ref.read(testFutureProvider.notifier).doSomethingAsync(); Navigator.of(context).pop(); Normally it is possible to check the mounted property like this: if(!mounted) return; or if(!context.mounted) return; How can I avoid…
I have an archaic solution for my problem, but it's quickly become cumbersome and not as robust. I want to switch to a riverpod provider and am studying how to do so, but I want to put this question out…
Building an app with Flutter and Riverpod, using a lot of: ref.watch(someProvider).when(data: (someData){ // render layout with data }, error: (err, stack) { // do stuff with error }, loading: (){ return LoadingScreen(); <---- }) The problem is that in…
Please check the two samples below. The first sample does not rebuild the Widgets [Possibly 'listeners' are not being 'notified'] The second sample works as expected To my understanding, i think all these two should work. Can someone brief me…
I looked at Riverpod's counter example and noticed it uses ConsumerWidget instead of ConsumerStatefulWidget. If ConsumerWidget can show state changes, is there any need to use ConsumerStatefulWidget? Why Riverpod, as a state management solution, has both stateful and stateless consumer…
Minimum reproducible code: class FooPage extends ConsumerWidget { @override Widget build(BuildContext context, WidgetRef ref) { final asyncValue = ref.watch(provider1); print('loading: ${asyncValue.isLoading}, value: ${asyncValue.valueOrNull}'); return Container(); } } final provider1 = StreamProvider<int>((ref) { final stream = ref.watch(provider2); return stream.maybeWhen( orElse: ()…