Replies: 1 comment
-
|
I'm not sure the value is worth the added confusion of having a larger API surface |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi – apps often need some providers that don't require a create function as they are expected to always have a value supplied via a
ProviderScopeoverride. To reduce boilerplate, for basic state types I use aMustOverrideProvider:I wonder if it would be useful to have this included in Riverpod itself, either by making the create function optional or preferably more explicitly via a modifier as with
familyandautoDispose? For example:Beta Was this translation helpful? Give feedback.
All reactions