Is it worth it to have a feature request like a promise.all or future.wait like for AsyncValues?

[sandbox-apps]

Guess that we have multiple asyncvalues per screen. In simplest scenario you would handle those things per entity. you place loading indicator per asyncvalue to handle their state. Im thinking that can we handle multiple AsyncValues combined into one?

[rrousselGit]

The difficulty is that most of the time, the combined AsyncValues return a different kind of object.

[rrousselGit]

There is a plan for a better solution. Although I am still in the process of looking for the correct solution.

[sandbox-apps]

I didn't know this will gain some atleast small discussion. Good to hear Im not just the only one in the community :D

[sandbox-apps]

This was came up because of the following

1. Some people do per entity solutions like for example using notifiers per entity.
2. Yes, you could create your own immutable class via freezed but others dont like to create and maintain immutable classes
   That's why the easiest escape route for now is to combine asyncValues

[sandbox-apps]

I just wonder how can i refresh the specific error from provider

[iamarnas]

There is an implementation in this thread that takes a list instead. #67 (comment)

final history = watch(historyProvider);
final favorites = watch(favoritesProvider);

return merge([history, favorites]).when(
  data: (_) {
    print(history.unwrap());
    print(favorites.unwrap());
  } ,
  // ...
);

I'm not understand what a point to merge history and favorites when they are already initialized with watch and can uses in the tree below?