ProviderRefBase and WidgetRef naming

[scopendo]

I noticed that with the 1.0 dev release that the ref passed to a provider's create function is now a ProviderRefBase, whereas a ConsumerWidget has WidgetRef.

I appreciate that these two need to be different but wondered if they could be named more consistently? In particular, whether it might be possible (with refactor) for ProviderRefBase to be named ProviderRef?

Just thinking that little consistencies like that might help people to follow Riverpod more easily.

[rrousselGit]

In the master channel, ProviderRefBase was renamed as "Ref"

"ProviderRef" is taken by "Provider((ProviderRef ref)"

[TimWhiting]

Expounding on this. Each provider type has a different "Ref" type to allow different methods on for example AutoDispose providers, StateProviders etc.

Provider((ProviderRef ref)
StateProvider((StateProviderRef ref)
FutureProvider((FutureProviderRef ref)
...

[scopendo]

Thank you both. Makes sense and pleased that it'll be moving to Ref soon 👍

…

On Sat, 30 Oct 2021, 19:21 Tim Whiting, ***@***.***> wrote: Expounding on this. Each provider type has a different "Ref" type to allow different methods on for example AutoDispose providers, StateProviders etc. Provider((ProviderRef ref) StateProvider((StateProviderRef ref) FutureProvider((FutureProviderRef ref) ... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#870 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAE6N6W2MR3W4U2TUUSEXPDUJQZR3ANCNFSM5HBGO7XA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.