resilify 1.0.6

Unified Result-based API handling for Dart & Flutter — works with http, Dio, Retrofit, Chopper, and WebSocket. No exceptions. Just results.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

1.0.6

Fixed

• Resolved pub.dev analysis failure caused by dart pub outdated --json crashing during dependency advisory parsing.
• Stabilized dependency resolution to ensure compatibility with pub.dev's pana analysis pipeline.
• Fixed documentation generation issues that prevented dartdoc from running successfully.
• Corrected documentation URL in pubspec.yaml to point to a valid and accessible resource.

Changed

• Adjusted dependency constraints (notably dio) to avoid triggering advisory parsing issues on pub.dev.
• Simplified dev dependency graph to improve analysis reliability and prevent toolchain conflicts.
• Improved overall package compatibility with pub.dev scoring system and analysis environment.

Documentation

• Added missing dartdoc comments across public APIs to improve documentation coverage and pub score.

1.0.5

Added

• Result.tap() — execute side effects (logging, debugging) on successful results without transforming the value. Great for inspecting data in the middle of a result chain:

  result.tap(print).tap(logToAnalytics).map(transformData);
  

• Enhanced code quality standards with stricter linting rules (upgraded lints to ^6.1.0) — the package now adheres to the latest Dart conventions and best practices for code style and correctness.

Fixed

• Trailing-comma lint warnings in lib/src/integrations/chopper_result.dart and lib/src/result.dart — package now passes dart analyze --fatal-warnings with zero issues.
• Removed deprecated transitive dependencies (build_resolvers, build_runner_core) that were flagged by pub.dev.

Changed

• Updated dev dependencies to latest versions:
  • lints: ^4.0.0 → ^6.1.0 for stricter code quality checks
  • retrofit_generator: ^8.0.0 → ^10.2.5
  • build_runner: ^2.4.0 → ^2.15.0
  • chopper_generator: ^8.0.0 → ^8.6.1
  • json_serializable: ^6.7.0 → ^6.13.2
  • test: ^1.25.0 → ^1.31.1
  • All transitive dependencies updated to latest compatible versions.

1.0.4

Added

• Failure.retryAfter — a Duration? field on Failure that surfaces the server's back-off hint from a Retry-After HTTP header. Populated automatically for 429 / 5xx responses by both HttpResultHandler and the Dio integration's mapDioException. Pair with RetryHelper.retry's delay parameter to honor the server's wait time exactly:

  result.errorOrNull?.retryAfter // Duration(seconds: 30) when present
  

• Failure.parseRetryAfter(String?) — static helper that converts the seconds form of an HTTP Retry-After header into a Duration. Returns null for null / blank / non-numeric input; clamps negatives to zero. The HTTP-date form is intentionally left to callers so the core library stays free of dart:io.

• platforms: declaration in pubspec.yaml (Android, iOS, Linux, macOS, Windows) so pub.dev surfaces verified platform support on the package page.

• documentation: link in pubspec.yaml pointing at the published dartdoc.

• Smoke tests for HttpResultHandler covering JSON GET/POST round-trips, query parameter merging, default-header propagation, 404 / 429 / 5xx mapping, Retry-After extraction, and parsing failures — closing the integration test gap flagged in the 1.0.3 audit.

Fixed

• Trailing-comma lint warnings in dio_result.dart and logger.dart so the package now ships with a clean dart analyze.

1.0.3

Added

• Result.fromNullable<T>(T?, {Failure Function()? onNull}) — bridge nullable APIs (cache lookups, firstWhereOrNull, etc.) into a Result<T> in one call.
• Result.zip2 and Result.zip3 — combine multiple results into a record (Result<(A, B)> / Result<(A, B, C)>), short-circuiting on the first failure left-to-right. Handy for parallel fetches with Future.wait.
• Result.collect<T>(Iterable<Result<T>>) — fold a list of results into a single Result<List<T>>, returning the first failure encountered.
• recoverWith extension on Future<Result<T>> — like recover, but the fallback callback may itself return a Result (so a fallback network call that also fails is surfaced as the final error).
• mapErrorAsync extension on Future<Result<T>> — async counterpart to the synchronous Result.mapError.

Changed

• RetryHelper.retry now accepts attemptTimeout. When set, each attempt is wrapped in Future.timeout; an exceeded timeout is converted into an Error(Failure.timeout()) and goes through the normal retryIf / maxAttempts machinery.

1.0.2

Added

• New Failure named constructors: Failure.forbidden (403), Failure.conflict (409), and Failure.rateLimit (429).
• Failure.fromStatusCode(int) — picks the most specific named constructor for a given HTTP status, falling back to badResponse for other 4xx and serverError for other 5xx.
• Failure.is4xx, Failure.is5xx, and Failure.isRetryable getters — drop-in predicates for RetryHelper.retryIf.
• onComplete extension on Result<T> — finally-style hook that fires for both Success and Error.
• flatten() extension on Result<Result<T>> — collapses one layer of nesting that flatMap chains often produce.

Changed

• RetryHelper.retry now accepts maxDelay to cap the wait between attempts and jitter (with an optional Random) to spread retries and prevent thundering-herd retry storms. Both default to no-op behavior, so existing call sites are unaffected.

1.0.1

Added

• Result.tryRun and Result.tryRunAsync — bridge throwing code into a Result<T> without writing try/catch at call sites. Both accept an optional onError to translate the caught object into a domain-specific Failure.
• mapError on Result<T> — transform the wrapped Failure without touching the success path. Useful for translating low-level transport failures into domain failures.
• errorOrThrow extension — symmetric counterpart to getOrThrow, returning the wrapped Failure or throwing a StateError on Success.

1.0.0 — Initial release

Added

• Core

  • Sealed Result<T> with Success<T> and Error<T> variants (Dart 3).
  • Structured Failure value type with named constructors: network, timeout, badResponse, parsing, unauthorized, notFound, serverError, cancelled, unknown.
  • Synchronous extensions: isSuccess, isError, dataOrNull, errorOrNull, getOrElse, getOrThrow, onSuccess, onError.
  • when, fold, map, flatMap on Result<T>.
  • Async helpers on Future<Result<T>>: mapAsync, flatMapAsync, recover.
  • Stream helpers on Stream<Result<T>>: mapStream, whereSuccess, whereError, dataStream, listenResult.
  • List helpers on Result<List<T>>: mapList, filter, whereResult, firstOrError.
  • RetryHelper.retry with exponential backoff, predicate-based retry, and per-attempt observer.

• Integrations (each opt-in via its own barrel file)

  • resilify_http.dart — HttpResultHandler for package:http.
  • resilify_dio.dart — DioResultHandler (incl. upload / download with progress) and ResultLoggerInterceptor.
  • resilify_retrofit.dart — .toResult() on Retrofit-generated futures.
  • resilify_chopper.dart — .toResult() on Chopper Response<T> futures with pluggable failure mappers.
  • resilify_websocket.dart — WebSocketResultHandler<T> with auto-reconnect and exponential backoff.