flutter-bloc-async-api

Handle REST API errors in Flutter Bloc by having repositories return a typed Future<Result<T>> instead of throwing exceptions. Blocs then await this result and emit consistent loading, success, or failure states without needing try/catch blocks at the call site.

Map Laravel 422 validation errors by converting HTTP outcomes into a fixed Failure union taxonomy. This includes a specific ValidationFailure variant for 422 field-error envelopes, allowing your Flutter Bloc to emit user-friendly failure messages derived directly from the typed error.

Cancel in-flight REST requests during pull-to-refresh by applying the restartable() transformer to your Bloc events. This safely cancels obsolete in-flight handling, preventing stale-data flicker when a new refresh or query event is triggered.

A sealed Result class works by encoding all REST API error cases into a single Failure union taxonomy. Repositories return this typed Result, ensuring the Bloc receives either a success value or a categorized failure, standardizing the async event flow.

Yes, this approach works specifically for Bloc-driven Flutter features like list loading and pull-to-refresh. It standardizes event flow to emit Loading, await the repository, and then emit Loaded or a failure message, applying restartable() for safe cancellation semantics.