Result
clean-minimal-api
| Result | clean-minimal-api | |
|---|---|---|
| 4 | 3 | |
| 752 | 590 | |
| - | - | |
| 7.3 | 0.0 | |
| 23 days ago | 12 months ago | |
| C# | C# | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Result
-
Advantages and disadvantages of FastEndpoints
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.
-
Why doesn't eager loading work with EF?
You could also use the Ardalis Guard Clause, Ardalis Result and Fluent Validation
-
The Operation Result Pattern
I use this generic package. https://github.com/ardalis/Result
-
Best practices for return values to handle success and failure conditions of business rules, exceptions, and returning a result?
For you're Result.cs , look at [Result pattern]https://github.com/ardalis/Result) as an example.
clean-minimal-api
-
Advantages and disadvantages of FastEndpoints
then how about not muddying up your controller/handler with a million attributes for swagger documentation? here's a sample swagger documentation class from nick-chapsas. they can stay away from your handler keeping them lean.
-
Open source dotnet 6 (MVC and Minimal API) reference projects
clean-minimal-api
-
Small to medium RESTful APIs with EF Core, what is a good architecture default?
You can use new minimal APIs. And you can see the example repo here: https://github.com/Elfocrash/clean-minimal-api
What are some alternatives?
FluentResults - A generalised Result object implementation for .NET/C#
aspnetskeleton2 - A foundation for building robust web applications on ASP.NET Core.
SmartEnum - A base class for quickly and easily creating strongly typed enum replacements in C#.
safe-routing - A C# source generator for ASP.NET Core razor pages and MVC controllers which produces strongly-typed identifiers for routes.
Specification - Base class with tests for adding specifications to a DDD model
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
eShopOnContainers - Cross-platform .NET sample microservices and container based application that runs on Linux Windows and macOS. Powered by .NET 7, Docker Containers and Azure Kubernetes Services. Supports Visual Studio, VS for Mac and CLI based environments with Docker CLI, dotnet CLI, VS Code or any other code editor. Moved to https://github.com/dotnet/eShop.
software-design-patterns - C# Design Patterns Tutorial Sample Code
CleanArchitecture - Clean Architecture Solution Template for ASP.NET Core
common-commons - A common set of C# extensions, models and helpers usually brought into personal projects of mine.