Trevin Miller
Trevin Miller
Technically yes, but the likelyhood of this failing to parse is zero since it's guaranteed to be well-formed. Generally `.unwrap()` is "fine" if you're positive it's a safe operation
Couldn't you do this by removing the `extends Object` bound on all of the generics (except for E)? I don't see any particular reason _why_ they're restricted to `Object`. Removing...
You could just add these to the repo itself and reference them by path
Working on a proper reproduction, now, but it's proving difficult. It'll likely take a few more days. I only created the issue now since it may have been a known...
Here's a working reproduction. I used `rxdart` to get the stream to work how I expect it to, so you'd need that as well. It seems to trigger the bug...
This is not a third party dependency issue. The print log continues to output to console, yet nothing appears on screen because Riverpod is not notifying the UI of the...
Great! You can ignore it completely. That's not where the issue is.
It's possible it could be replaced with a normal stream controller with a global variable that also stores the most recently emitted value, but I'm uncertain if this would be...
I have modified the code from my phone. It may or may not compile and may or may not reproduce the issue. I am presently unable to test it. ```...
> Why are you listening to that stream inside onDispose (and then immediately call cancel)? It's not immediately calling cancel, just passing the `.cancel` function to `onDispose`. No particular reason...