Remi Rousselet

I can run your example. I just need a bit of time to investigate the matter in depth. For now I'm on other features

Pretty sure that's not a loop, just an exponential amount of rebuild. The first provider emits two updates (persist + initialized) The second has 3 (persist + initial + rebuild...

Wait, what's that? > final items = await ref.watch(cursorProvider(id, cursor: page).future); A provider is watching itself with the exact same args? How is that expected to ever resolve? I'm surprised...

> Probably because I'm mocking "too much" of the storage logic, but I'm unsure how to mock "less" than that. Let me know what I could do to improve this...

It's 3.0 stuff

No this is unrelated

Ref.listen or WidgetRef.listenManual

The main issue is that this: ```dart await ref.read(provider.notifier).doSomethingAsync(); ``` is equally unsafe. I'm heavily considering deprecating ref.read altogether, in favour of the approach taken by mutations

Isn't that already the case?

How would Riverpod know what that is?