op_result 0.2.2

op_result: ^0.2.2 copied to clipboard

Maintenance #

• Bumped version to 0.2.2 for consistency and dependency updates.
• No functional changes.

Initial Public Release #

• Added support for nullable success values (T?) in OpResult.success()
• Improved failure handling by supporting both single and multiple errors
• Refactored OpResult.success() to use a positional argument instead of a named parameter

Breaking Changes #

• Refactored OpResult.success() to use a positional argument instead of data:
  • Now, call OpResult.success(value) instead of OpResult.success(data: value).
  • Example:
    • Before: OpResult.success(data: user);
    • Now: OpResult.success(user);
• Refactored OpResult to support multiple errors:
  • Replaced _error (single error) with _errors (list of errors).
  • OpResult.failure() now supports both single and multiple errors via a factory constructor:
    • OpResult.failure(singleError)
    • OpResult.failure([multipleErrors])

Improvements #

• Unified failure handling:
  • Removed OpResult.failure({required OpResultError<E> error}) in favor of a flexible factory constructor.
  • Supports passing either a single error or a list of errors dynamically.
• Ensured failure() cannot receive an empty list, preventing invalid states.
• Refactored error access:
  • error → Returns the first error (default for single-error scenarios).
  • errors → Provides full access to all errors when multiple exist.

• Initial version.