snapsl

Results 53 comments of snapsl

[Suggestion] Convenience methods for MutationState (check for loading, success, error)

Great suggestion. This further aligns `MutationState` with `AsyncValue`.

Bad state: Tried to read a provider from a ProviderContainer that was already disposed

Hi , again share a minimal reproducible example.

Throws Bad state: Cannot use "ref" after the widget was disposed, when using ref in dispose callback, even though widget is still mounted

#1610

Add exception handling to 'ref.refresh()'

> You're not even awaiting it. Thanks... Uncaught exceptions in callbacks are forwarded to the PlatformDispatcher ([link](https://docs.flutter.dev/testing/errors#errors-not-caught-by-flutter)). If these are not handled properly, such “errors” are logged for no reason.

Add exception handling to 'ref.refresh()'

Yes, the error is that the rebuild of the provider failed, e.g. due to a failed network request. This is logged by provider observer or the network service. However, since...

Add exception handling to 'ref.refresh()'

Hi @rrousselGit, thank you for taking your time and reviewing this feature request. I understand that this is not a critical issue. Maybe some people also rely on refresh to...

Debouncing example app locks up

I don't see an issue here. @sisyfus you can use discord or the discussion section to ask questions.

Debouncing example app locks up

@sisyfus I haven't registered any lockups, but some debugging has uncovered the problem. Can `ref.refresh(activityProvider.future)` throw exceptions? I assumed this is handled by Riverpod.🤔

Debouncing example app locks up

@AhmedLSayed9 thank you for confirming this. I hoped that `ref.refresh()` would handle this. It would be nice to remove the exception handling from the UI code, as AsyncValue does. Current...

Debouncing example app locks up

@sisyfus can you test if the app also lockup in release mode? @rrousselGit can you take a look into this?😉 Also, what do you think about adding exception handling for...