ProviderListener missing events about riverpod

[rrousselGit]

The thing is, Providers voluntarily do not call listeners immediately on change

This is for performance and maintainability reasons.

So you're better off with a custom WhateverListener for special objects

[tbm98]

In the documentation.
Even if a provider changes many times in a quick succession, onChange will be called only once, at the end of the frame.
but I think it should triggers onChange if state is changed instead of call only once at the end of the frame

[rrousselGit]

What's the purpose?

[tbm98]

In a task, maybe something I want to pass more than one event to UI handle.
an example: loading dialog is showing and my http request done, then I want to dismisDialog and show snackbar for result success or fail.

[tbm98]

so still can pass successEvent to UI do both dismisDialog and showSnackbar but I think it will be more flexible if it is managed from providers.

[rrousselGit]

Maybe you shouldn't use StateProvider and instead use StateNotifierProvider with a custom StateNotifier

[tbm98]

What is that better than StateNotifier if I use StateNotifierProvider ?

[rrousselGit]

Actually, I'm not sure what you're trying to accomplish by writing:

context.read(eventProvider).state = LoadingEvent();
context.read(eventProvider).state = ShowSnackbarEvent();

StateNotifier is not an event queue, nor are providers.

Why not write showDialog/Navigator.pop directly inside the onPressed?

[tbm98]

Just for example. Actually I call it from providers. So if I want to pass event like a queue to UI then what should i do ? Vào 12:54, Th 5, 13 thg 8, 2020 Remi Rousselet <[email protected]> đã viết:

…

Actually, I'm not sure what you're trying to accomplish by writing: context.read(eventProvider).state = LoadingEvent(); context.read(eventProvider).state = ShowSnackbarEvent(); StateNotifier is not an event queue, nor are providers. Why not write showDialog/Navigator.pop directly inside the onPressed? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMRATJFY5NH4JELG2S54HNTSAN5YTANCNFSM4P5UKVMQ> .

[rrousselGit]

Maybe do context.read(eventProvider).addListener(...)

[tbm98]

I think addListener will be difficult to use in StatelessWidget or HookWidget because it should only be called once. So ProviderListener was born as a solution to the above problem and I think it should work like what addListener does as well.

[tbm98]

Yes. maybe I need another way to solve it.
Thanks !