s9th

Results 5 comments of s9th

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

in 90% of cases in my project I don't need the value itself. E.g. if I want to show a toast on successful mutation, or an error (without specifying the...

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

I also wanted to add that in the brief time that I worked with mutations, I already fell into a trap of writing `mutation is PendingMutation` instead of `mutation.state` a...

Using ref.watch/ref.listen on mutation in a widget produces "(setState() or markNeedsBuild() called during build." error

I could reproduce it here Without ref.listen(counterMutation) error doesn't happen. It also happens on ref.watch(counterMutation) ```dart import 'package:flutter/material.dart'; import 'package:flutter_riverpod/experimental/mutation.dart'; import 'package:flutter_riverpod/flutter_riverpod.dart'; import 'package:riverpod_annotation/riverpod_annotation.dart'; part 'main.g.dart'; void main() { runApp(ProviderScope(child:...

Using ref.watch/ref.listen on mutation in a widget produces "(setState() or markNeedsBuild() called during build." error

Strangely enough for me it wasn't reproducing with normal providers, just with mutations

Using ref.watch/ref.listen on mutation in a widget produces "(setState() or markNeedsBuild() called during build." error

@rrousselGit were you able to reproduce it from the examples?