Expose an interface for providers with notifiers

[CardosoShlomo]

I wish to be able to write something like ref.write(provider) or ref.notify(provider) instead of ref.read(provider.notifier)

I found that the providers that have a notifier do not have a unique supper class in common
so I wonder if we can create a class like HasNotifierProvider that extends BaseProvider and holds the notifier getter
then make AsyncNotifierProviderBase, NotifierProviderBase and _StateProviderBase extends HasNotifierProvider instead of BaseProvider and override the notifier

then I'll be able to add extensions on Ref and WidgetRef

extension on Ref {
  notify<T>(HasNotifierProvider<T> provider) => read(provider.notifier);
}

[CardosoShlomo]

@rrousselGit Is there a reason why Ref and WidgetRef do not share an abstract class?

[jakeaaron]

@CardosoShlomo

@rrousselGit Is there a reason why Ref and WidgetRef do not share an abstract class?

To answer your question with the docs: https://riverpod.dev/docs/essentials/faq#why-is-there-no-shared-interface-between-ref-and-widgetref