Michael Altmann
Michael Altmann
Our teams use this library very heavily. Our vote would be ``` Result.Create(bool) => Result.SuccessIf(bool) Result.CreateFailure(bool) => Result.FailIf(bool) Result.Ok() => keep as it is and add Success() Result.Fail() => keep...
I added an PR with the default(T) solution.
Yes, in 99% I need this conversion in situations which I have to convert a failed result to another type of result. I will have a look to Map(...) and...
@vkhorikov I have now two new methods but what should I do in the success case? ```` c# public static Result MapFailure(this Result result) { if (result.IsFailure) return Result.Fail(result.Error); return...
@space-alien @vkhorikov Our team don't like this railway-orientied approach in some cases. Therefore a MapFailure() method would be very useful to us.
Hi, thanks for your pr. Can you please add some information/motivation why you need this enhancement.
Thanks for the feedback! Great that you think that the library is useful. :)
Thank you! Never thought about that.
@bogdanpolak Today I added the sponsor button to my FluentResults project. So it is now possible to donate money via paypal. I'am looking forward to the first incoming donations. :)...
Hi guys! First: ```ToResult(...)``` is not what you want. See https://github.com/altmann/FluentResults#converting for details - ```ToResult()``` is for converting from ```Result``` to ```Result``` or vice versa. Second: This functional magic was...