Result VS GuardClauses

Using the Nuget Package Ardalis.Result for mapping result objects to HTTP Response Codes and associated objects; FastEndpoint has its own way of approaching this problem, which seems to be to hang everything off an "Endpoint" and optionally using Swagger to redundantly describe the route's behavior; this seems like a step backwards from more advanced Web frameworks in other languages. The advantage of Ardalis.Result should be clear - each closed form of Ardalis.Result can have its own knowledge of what it does, and therefore automatically describe the abstract transformations it does on a request. In functional programming, this "abstract transformation" is typically called a monad transformer or Arrow. Once you have a type that describes the abstract transformation, plugging that into Swagger should be straight-forward.

You could also use the Ardalis Guard Clause, Ardalis Result and Fluent Validation

I use this generic package. https://github.com/ardalis/Result

For you're Result.cs , look at [Result pattern]https://github.com/ardalis/Result) as an example.

You could also use the Ardalis Guard Clause, Ardalis Result and Fluent Validation

Here is an example how one would make sure our order total is valid. For this purpose I use an amazing library called GuardClauses.

GuardClauses

I'm guessing it's just a port of Ardalis' Guard class since he helped a lot with Microsoft's web projects.

The Guard Clauses are from: https://github.com/ardalis/GuardClauses

In terms of readability concerns, I definitely hear you on that. Using something like this can cut down on code bloat that comes with param validation and help with readability.

It's made by Ardalis, who wrote Microsoft's architectural guide for ASP.NET Core Web APIs. I like his GuardClauses library too.