asyncredux-error-handling
Implement comprehensive error handling for actions. Covers the `wrapError()` method for action-level error wrapping, GlobalWrapError for app-wide error transformation, ErrorObserver for logging/monitoring, and the error handling flow (before → reduce → after).
Best use case
asyncredux-error-handling is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement comprehensive error handling for actions. Covers the `wrapError()` method for action-level error wrapping, GlobalWrapError for app-wide error transformation, ErrorObserver for logging/monitoring, and the error handling flow (before → reduce → after).
Teams using asyncredux-error-handling should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/asyncredux-error-handling/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How asyncredux-error-handling Compares
| Feature / Agent | asyncredux-error-handling | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement comprehensive error handling for actions. Covers the `wrapError()` method for action-level error wrapping, GlobalWrapError for app-wide error transformation, ErrorObserver for logging/monitoring, and the error handling flow (before → reduce → after).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Error Handling in AsyncRedux
AsyncRedux provides a comprehensive error handling system with multiple layers: action-level wrapping, global error transformation, and error observation for logging/monitoring.
## Error Flow and Action Lifecycle
When errors occur during action execution:
1. If `before()` throws an error, the reducer doesn't execute and state remains unchanged
2. If `reduce()` throws an error, execution halts without state modification
3. The `after()` method **always** runs, even when errors occur (like a `finally` block)
**Processing order:** `wrapError()` → `GlobalWrapError` → `ErrorObserver`
## Throwing Errors from Actions
Actions can throw errors using `throw`. When an error is thrown, the reducer stops and state is not modified:
```dart
class TransferMoney extends AppAction {
final double amount;
TransferMoney(this.amount);
AppState? reduce() {
if (amount == 0) {
throw UserException('You cannot transfer zero money.');
}
return state.copy(cash: state.cash - amount);
}
}
```
## UserException for User-Facing Errors
`UserException` is a built-in class for errors that users can understand and potentially fix (not code bugs):
```dart
class SaveUser extends AppAction {
final String name;
SaveUser(this.name);
Future<AppState?> reduce() async {
if (name.length < 4)
throw UserException('Name must have 4 letters.');
await saveUser(name);
return null;
}
}
```
When a `UserException` is thrown, it's added to a special error queue in the store and can be displayed via `UserExceptionDialog`.
### Displaying UserExceptions
Wrap your home page with `UserExceptionDialog` below both `StoreProvider` and `MaterialApp`:
```dart
UserExceptionDialog<AppState>(
onShowUserExceptionDialog: (context, exception) => showDialog(...),
child: MyHomePage(),
)
```
## Action-Level Error Wrapping with wrapError()
The `wrapError()` method acts as a catch block for entire actions. It receives the original error and stack trace, and must return:
- A modified error (to transform the error)
- `null` (to suppress/disable the error)
- The unchanged error (to pass it through)
```dart
class LogoutAction extends AppAction {
@override
Object? wrapError(Object error, StackTrace stackTrace) {
return LogoutError("Logout failed", cause: error);
}
Future<AppState?> reduce() async {
await authService.logout();
return state.copy(user: null);
}
}
```
### Mixin Pattern for Reusable Error Handling
Create mixins for consistent error transformation across multiple actions:
```dart
mixin ShowUserException on AppAction {
String getErrorMessage();
@override
Object? wrapError(Object error, StackTrace stackTrace) {
return UserException(getErrorMessage()).addCause(error);
}
}
class LoadDataAction extends AppAction with ShowUserException {
@override
String getErrorMessage() => 'Failed to load data. Please try again.';
Future<AppState?> reduce() async {
var data = await api.loadData();
return state.copy(data: data);
}
}
```
### Suppressing Errors
Return `null` from `wrapError()` to suppress errors without further propagation:
```dart
@override
Object? wrapError(Object error, StackTrace stackTrace) {
if (error is CancelledException) {
return null; // Silently ignore cancellation
}
return error;
}
```
## Global Error Handling with GlobalWrapError
`GlobalWrapError` processes all action errors centrally. This is useful for transforming third-party library errors (like Firebase or platform exceptions):
```dart
var store = Store<AppState>(
initialState: AppState.initialState(),
globalWrapError: MyGlobalWrapError(),
);
class MyGlobalWrapError extends GlobalWrapError {
@override
Object? wrap(Object error, StackTrace stackTrace, ReduxAction<AppState> action) {
// Transform platform exceptions to user-friendly messages
if (error is PlatformException && error.code == "Error performing get") {
return UserException('Check your internet connection').addCause(error);
}
// Transform Firebase errors
if (error is FirebaseException) {
return UserException('Service temporarily unavailable').addCause(error);
}
// Pass through all other errors unchanged
return error;
}
}
```
Return `null` from `GlobalWrapError.wrap()` to suppress errors globally.
## Error Observation with ErrorObserver
`ErrorObserver` receives all errors with context about the action and store. Use it for logging, monitoring, or analytics:
```dart
var store = Store<AppState>(
initialState: AppState.initialState(),
errorObserver: MyErrorObserver<AppState>(),
);
class MyErrorObserver<St> implements ErrorObserver<St> {
@override
bool observe(
Object error,
StackTrace stackTrace,
ReduxAction<St> action,
Store<St> store,
) {
// Log the error
print("Error during ${action.runtimeType}: $error");
// Send to crash reporting service
crashlytics.recordError(error, stackTrace);
// Return true to rethrow, false to swallow
return true;
}
}
```
The `observe` method returns:
- `true` to rethrow the error (default behavior)
- `false` to swallow the error silently
## UserExceptionAction for Mid-Action Errors
For showing error feedback while allowing the action to continue (without stopping execution):
```dart
class ConvertAction extends AppAction {
final String text;
ConvertAction(this.text);
Future<AppState?> reduce() async {
var value = int.tryParse(text);
if (value == null) {
// Show error but continue action
dispatch(UserExceptionAction('Please enter a valid number'));
return null; // No state change
}
return state.copy(counter: value);
}
}
```
## Checking Action Failure Status
### Using ActionStatus
After dispatching with `dispatchAndWait()`, check the status:
```dart
var status = await store.dispatchAndWait(SaveAction());
if (status.isCompletedOk) {
Navigator.pop(context);
} else if (status.isCompletedFailed) {
var error = status.wrappedError;
print('Save failed: $error');
}
```
**ActionStatus properties:**
- `isCompletedOk`: Action finished without errors
- `isCompletedFailed`: Action encountered errors
- `originalError`: The error as thrown from `before` or `reduce`
- `wrappedError`: The error after transformation by `wrapError()`
### Using isFailed in Widgets
Check action failure state in the UI:
```dart
Widget build(BuildContext context) {
if (context.isFailed(LoadDataAction)) {
var exception = context.exceptionFor(LoadDataAction);
return Column(
children: [
Text('Error: ${exception?.message}'),
ElevatedButton(
onPressed: () => context.dispatch(LoadDataAction()),
child: Text('Retry'),
),
],
);
}
if (context.isWaiting(LoadDataAction)) {
return CircularProgressIndicator();
}
return DataWidget(data: context.state.data);
}
```
The error is cleared automatically when the action is dispatched again.
To manually clear the error:
```dart
context.clearExceptionFor(LoadDataAction);
```
## Testing Error Handling
Test that actions fail with expected errors:
```dart
test('action throws UserException for invalid input', () async {
var store = Store<AppState>(initialState: AppState.initialState());
var status = await store.dispatchAndWait(SaveUser('abc')); // too short
expect(status.isCompletedFailed, isTrue);
var error = status.wrappedError;
expect(error, isA<UserException>());
expect((error as UserException).msg, 'Name must have 4 letters.');
});
```
Test multiple exceptions via the error queue:
```dart
test('multiple actions accumulate errors', () async {
var store = Store<AppState>(initialState: AppState.initialState());
await store.dispatchAndWaitAll([
InvalidAction1(),
InvalidAction2(),
InvalidAction3(),
]);
var errors = store.errors;
expect(errors.length, 3);
expect(errors[0].msg, 'First error message');
});
```
## Complete Store Setup with Error Handling
```dart
var store = Store<AppState>(
initialState: AppState.initialState(),
globalWrapError: MyGlobalWrapError(),
errorObserver: MyErrorObserver<AppState>(),
actionObservers: [Log.printer(formatter: Log.verySimpleFormatter)],
);
class MyGlobalWrapError extends GlobalWrapError {
@override
Object? wrap(Object error, StackTrace stackTrace, ReduxAction<AppState> action) {
if (error is SocketException) {
return UserException('No internet connection').addCause(error);
}
return error;
}
}
class MyErrorObserver<St> implements ErrorObserver<St> {
@override
bool observe(Object error, StackTrace stackTrace, ReduxAction<St> action, Store<St> store) {
// Skip logging UserExceptions (they're expected)
if (error is! UserException) {
crashlytics.recordError(error, stackTrace);
}
return true;
}
}
```
## References
URLs from the documentation:
- https://asyncredux.com/sitemap.xml
- https://asyncredux.com/flutter/advanced-actions/errors-thrown-by-actions
- https://asyncredux.com/flutter/advanced-actions/wrapping-the-reducer
- https://asyncredux.com/flutter/basics/failed-actions
- https://asyncredux.com/flutter/advanced-actions/before-and-after-the-reducer
- https://asyncredux.com/flutter/basics/store
- https://asyncredux.com/flutter/testing/testing-user-exceptions
- https://asyncredux.com/flutter/basics/wait-fail-succeed
- https://asyncredux.com/flutter/miscellaneous/logging
- https://asyncredux.com/flutter/advanced-actions/action-statusRelated Skills
implementing-error-handling
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
golang-error-handling
Go error handling review. Use when checking error wrapping, context propagation, or error checking patterns. Ensures proper error chains, context usage, and nil checks.
Global Error Handling
Your approach to handling global error handling. Use this skill when working on files where global error handling comes into play.
Fundamental Attribution Error
Over-attributing others' behavior to their character while under-weighting situational factors that shape their actions
fp-ts-errors
Handle errors as values using fp-ts Either and TaskEither for cleaner, more predictable TypeScript code. Use when implementing error handling patterns with fp-ts.
fix-validation-errors-with-overlays
Use when you have lint errors but can't modify the source spec, or need to add missing descriptions/tags via overlay
error-tracking
Add error tracking and performance monitoring to your project services. Use this skill when adding error handling, creating new controllers/routes, instrumenting background jobs, or tracking performance. Supports Sentry, Datadog, and other monitoring solutions. ALL ERRORS MUST BE CAPTURED - no exceptions.
error-root-analyzer
Comprehensive error analysis and root cause resolution. Use when programs fail, crash, or produce errors during execution. This skill performs deep debugging by identifying root causes (not just surface-level symptoms), conducting thorough module reviews to uncover related bugs and exceptions, and implementing holistic fixes that address all discovered issues.
error-handling
Comprehensive error handling patterns for Splits Network services and apps
error-handling-patterns
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.
error-diagnostics-error-analysis
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.
error-debugging-error-analysis
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.