Releases: co-IT/CSharpFunctionalExtensions.HttpResults
Releases · co-IT/CSharpFunctionalExtensions.HttpResults
v1.2.0
What's Changed
- feat: add
ToServerSentEventsHttpResultmethod by @DerStimmler in #30
Full Changelog: v1.1.0...v1.2.0
v1.1.0
v1.0.1
What's Changed
- feat: add analyzer
CFEHTTPR004to check for parameterless constructor in error mapper class by @DerStimmler in #26 - perf: improve performance by reusing error mapper instances in extension methods by @DerStimmler in #26
Full Changelog: v1.0.0...v1.0.1
v1.0.0
Stable Release! 🚀
v0.9.5
What's Changed
- ci: create test result & coverage reports by @DerStimmler in #22
- docs(readme): improve readme by @DerStimmler in #23
Full Changelog: v0.9.4...v0.9.5
v0.9.4
What's Changed
- chore: include xml docs in package
- perf: reduce package size
Full Changelog: v0.9.3...v0.9.4
v0.9.3
v0.9.2
v0.9.1
What's Changed
- widen supported range of CSharpFunctionalExtensions versions by @DerStimmler in #18
- add tests for different CSharpFunctionalExtensions versions by @DerStimmler in #18
- update dependencies by @DerStimmler in #18
Full Changelog: v0.9.0...v0.9.1
v0.9.0
Breaking
- use method instead of func for custom error mapping by @DerStimmler in #17
- To migrate, simply change all
MapFuncs in your custom error mappers that implementIResultErrorMapperto aMapmethod.public Func<DocumentMissingError, NotFound<string>> Map => error => TypedResults.NotFound(error.DocumentId); //becomes public NotFound<string> Map(DocumentMissingError error) => TypedResults.NotFound(error.DocumentId);
- To migrate, simply change all
What's Changed
- enhance custom error mapper flexibility by applying in/out variances to mapper types by @DerStimmler in #17
Full Changelog: v0.8.0...v0.9.0