Replies: 1 comment 5 replies
-
+1 on this issue. Another use case would be a settings page for a remote device, where you mainly load settings from remote device, but when the user change settings, you want to "force" some value to be the changed settings, instead of loading them again (loading again introduces delay). I think we should be able to change the "cached" value inside FutureProvider. @rrousselGit Would you please give some comments on this topic? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I could just use
StateNotifier
but if I could edit the data inFutureProvider
likeStateProvider
, that would clear some boilerplate and it would make my life easy at least.Use Case
Let's say we have a
FutureProvider
that fetches comments of a post. When a user adds a new comment to the post, that'd be easier to add the new comment to the list inFutureProvider
.RiverPod could have something like
FutureStateProvider
that combines bothFutureProvider
andStateProvider
.Beta Was this translation helpful? Give feedback.
All reactions