vonage-dotnet-sdk VS OneOf

Previously, we built an Optional and showed an existing set based on Language-Ext, but various libraries also offer Monad implementations. In the case of our SDK, we deliberately avoided relying on external libraries like Language-Ext. Indeed, Monads are a part of the SDK's public API, and relying on an external library would introduce a dependency over which we would have limited control.

This is the first post in a series that aims to demystify Monads and help you benefit from them, using real-life examples from our .NET SDK. Watch my related talk "Throw exceptions... out of your codebase" which was more about Monads than it was about exceptions, even if the title says otherwise.

OneOf

Inclusive, para suportar esse tipo de funcionalidade, foi criada a biblioteca OneOf: mcintyre321/OneOf: Easy to use F#-like ~discriminated~ unions for C# with exhaustive compile time matching (github.com)

Then I found discussion of the OneOf package, and then found some simpler Result code. I tried using that code but I found the use of Match and lambdas meant I couldn't simply break out of the loop in my example.

Until that feature lands there's this https://github.com/mcintyre321/OneOf which is pretty nice.

Yep, it's called result pattern, aforementioned above. There was two highlighted implementations - OneOf, FluentResults.

No he didn't. He made a video of the OneOf library. Not this one.

We already have OneOf https://github.com/mcintyre321/OneOf I've used it in Production multiple times and it's an awesome way to keep everything strongly typed and eliminate null reference exceptions.