Remi Rousselet comments

Results 1776 comments of


                                            Remi Rousselet

ref.read() gets previous state, instead of the same value as next from ref.listen()

What are you using it for? The behavior of `ref` inside listeners/life-cycles is undetermined/untested. I wouldn't be able to tell you for sure what happens in some cases or whether...

ref.read() gets previous state, instead of the same value as next from ref.listen()

Sounds reasonable.

ref.read() gets previous state, instead of the same value as next from ref.listen()

I've just realised that this is a duplicate of https://github.com/rrousselGit/riverpod/issues/4185

Different behavior when listening to streams (from drift) using StreamProvider vs StreamBuilder

I don't the time to investigate third-party packages. If this is important for you, I'd suggest looking into the issue yourself :)

Different behavior when listening to streams (from drift) using StreamProvider vs StreamBuilder

Running the example in the top post, I do not have the described behaviour when using 3.0.0 I only see a single `map Called with []` log. Do you still...

ref.watch returns a value other than ref.read

I'd need a complete example. As is, this doesn't make sense to me

ref.watch returns a value other than ref.read

My guess is more that your provider got disposed after `read`, and therefore `watch` created a new value

ref.watch returns a value other than ref.read

What's wrong here exactly? Your provider wasn't listener so it got disposed.

ref.watch returns a value other than ref.read

You don't watch the provider until 140ms elapse. So it can get disposed before then. And your Inc method calls ref.invalidateSelf, which also causes the provider to be disposed. Your...

ref.watch returns a value other than ref.read

It does. Hence why there's no dispose between the second `AsyncLoading()` and a`AsyncData(1)` The second dispose and reset to `null` is because you called invalidateSelf