Can you recommend how to design a reusable widget with Riverpod as a reusable state?

[mgolokhov]

Hello,
Thank you for the great library :)

Can you recommend how to design a reusable widget with Riverpod as a reusable state?

As an example, could be a Table widget with

base actions:

• load
• refresh
• sortBy

base states:

• loading
• refreshing
• error
• errorWithData
• data

The first try was to use StateNotifier with states baked by Freezed package.

How can I give through Table constructor base provider and then ref.watch(baseTableProvider) base states and trigger actions by ref.read(baseTableProvider)?

[rrousselGit]

Do you have a more specific question? This is a bit too broad.

[mgolokhov]

Most examples show how to work with the specific provider as final variable like ref.watch(specificProvider).when(...handle states as union...)
Is it possible to watch providers in a more dynamic way something like ref.watch(baseProvider).when(...)?

[mgolokhov]

For now, the only way I see that BaseTableWidget should not have BaseTableProvider inside and expose only callbacks
and a developer should make a bit more piping
ex onBuild

 child = ref.watch(customTableProvider).when(
          loading: () => buildLoadingView(),
          data: (TableViewModel newVm) => buildTableView(newVm),
          error: () => buildErrorView(),
          refreshing: (TableViewModel oldVm) => buildRefreshing(oldVm),
          );

Example for action onRefresh:

        ref.read(customTableProvider.notifier).refresh();

[rrousselGit]

I still don't quite understand what you're trying to do.

Are you trying to use Riverpod to avoid having to make statefulwidgets?

[mgolokhov]

Yes, it's one of the points.
How can I design a common Widget with Riverpod as state manager,
so a developer can reuse that Widget (reuse actions and state and some flow) with minimal boilerplate and still have the possibility to expand functionality.

[rrousselGit]

Riverpod isn't meant to be a solution for local widget state. Providers are for shared state only

If you want a local state framework, you can have a look at flutter_hooks, which is typically combined with Riverpod, but for local widget state.

[neiljaywarner]

i also would like to have some guidance here, for example is it "unwise" to put it in a shared components repo..
the tip I got from SO or something is making a provider static under the things it's providing