asyncredux-actions-no-state-change

To run side effects in AsyncRedux without mutating the app state, your action's reduce() method should return null. This allows you to execute logging, API calls, or coordinate other actions while keeping the current state intact.

Yes, an AsyncRedux action can dispatch and coordinate other actions without directly changing AppState. By returning null from the reduce() method, the action triggers side effects or navigation while ensuring the state remains unchanged.

To perform async work in Flutter using AsyncRedux without triggering a state update, return a Future<AppState?> that resolves to null from the reduce() method. This executes asynchronous orchestration while preventing state mutations.

Yes, returning null from reduce() in AsyncRedux prevents state changes while allowing API calls. This mechanism is designed specifically for scenarios requiring side effects, such as logging or fetching data, without altering the existing state.

The best way to handle logging and navigation in AsyncRedux without state mutations is to return null from the reduce() method. This approach executes necessary side effects and coordination tasks while explicitly preserving the current AppState.