Full Changelog: v1.1.2502.2013...v1.1.2502.2422
Breaking Changes ⚠️
Deprecated Methods
Tap()method forMaybe<TIn>has been deprecated in favor ofTapIfSome()/TapIfNone().Map()method forMaybe<TIn>has been deprecated in favor ofMatch(), consistent with theMatchmethod forResult<TIn>.
New Features ✨
This release introduces extensive support for async workflows and method chaining for both Maybe<TIn> and Result<TIn>.
-
Bind/BindAsync Methods for
Maybe<TIn>:- Support for mixed synchronous/asynchronous handler workflows.
- Fluent composition with both void and return-type handlers.
- Support for method chaining.
-
Match/MatchAsync Methods for
Maybe<TIn>:- State-aware pattern matching capabilities.
- Async-compatible result projections.
-
TapIfSome/TapIfNone Methods for
Maybe<TIn>:- Added async side effects support with
TapIfSomeAsync/TapIfNoneAsync.
- Added async side effects support with
-
Ensure/EnsureAsync Methods for
Result<TIn>:- Support for
Try<TIn>andTryAsync<TIn>. - Chainable
Try<TIn>andTryAsync<TIn>withResult<TIn>.
- Support for
-
Bind/BindAsync Methods for
Result<TIn>:- Support for mixed synchronous/asynchronous handler workflows.
- Chainable
Try<TIn>andTryAsync<TIn>withResult<TIn>andTask<Result<TIn>>. - Fluent composition with both void and return-type handlers.
-
Match/MatchAsync Methods for
Result<TIn>:- Chainable
Try<TIn>andTryAsync<TIn>withResult<TIn>andTask<Result<TIn>>. - State-aware pattern matching capabilities.
- Async-compatible result projections.
- Chainable
-
Added support for
Bind/BindAsyncmethods forTry<TIn>to enable:- Seamless integration with
Result<TIn>andMaybe<TIn>types - Enhanced error handling and propagation
- Seamless integration with
Improvements 📈
Documentation Updates
- Added complete usage examples for core API surface
- Expanded conceptual explanations for:
- Error handling strategies
- Async/Await best practices
- Composition patterns with
BindandMatch
- Included troubleshooting guide for common scenarios
- Improved API reference documentation with XML doc enhancements
Fixes 🛠️
- Resolved a bug in
MatchAsyncmethods that caused incorrect result projections under specific conditions. - Corrected documentation inconsistencies and improved XML comments for better IntelliSense support.