async_redux
async_redux copied to clipboard
Flutter Package: A Redux version tailored for Flutter, which is easy to learn, to use, to test, and has no boilerplate. Allows for both sync and async reducers.
We have noticed issues when comparing viewmodels for equality and it is affecting testing. The below code demonstrates the outcome of comparisons: ``` import 'package:async_redux/async_redux.dart'; import 'package:flutter/foundation.dart'; import 'package:flutter_test/flutter_test.dart'; class...
Hi, I have to say great project. I've been in love with redux for awhile now. But the boilerplate code always truns my colleges of. Now to my question. Have...
How to implement protection against too often heavy operations? For instance, if I pressed the "Save" button quickly several times. I don't want to save multiple times. I want to...
Hello, Firstly want to say I love the project. Very helpful and understandable state management tool. I am looking to run the business logic tests independently of flutter, which I...
I'm a Flutter noob trying to get the nice state management stack that I'm accustomed to from [react-redux](https://react-redux.js.org/api/hooks). The combination of `useSelector` and `useDispatch` hooks is the cleanest and most...
UserExceptionDialog was written before flutter had [Navigator 2.0](https://docs.flutter.dev/go/navigator-with-router) and the new [scaffold-messenger](https://docs.flutter.dev/release/breaking-changes/scaffold-messenger) At the moment it still requires to place a `UserExceptionDialog` in between the MaterialApp and the HomePage Widget,...
After seeing a couple of the existing devtools extensions in action, I thought that it would be really great to have an extension for async_redux. Have not looked at the...
I migrated from some custom waits to the new `isWaiting(actionOrTypeOrList)`. While `context.isWaiting` does rebuild the widget, using `isWaiting(actionOrTypeOrList)` in a view model factory does not rebuild. Is this expected?
in the documentation (https://pub.dev/packages/async_redux#giving-better-error-messages) the code: ` class LogoutAction extends ReduxAction { @override Future reduce() async { ... } @override Object wrapError(error) => LogoutError("Logout failed.", cause: error); }` is incorrect....
The mixins only check for `ConnectivityResult.none`. If the result list for example contains only `ConnectivityResult.bluetooth` then there is effectively no internet available. Does it make sense to invert the check...