safe-routing
A C# source generator for ASP.NET Core razor pages and MVC controllers which produces strongly-typed identifiers for routes. (by daviddotcs)
Result
A result abstraction that can be mapped to HTTP response codes if needed. (by ardalis)
| safe-routing | Result | |
|---|---|---|
| 1 | 4 | |
| 28 | 755 | |
| - | - | |
| 8.5 | 7.3 | |
| 12 days ago | 5 days ago | |
| C# | C# | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
safe-routing
Posts with mentions or reviews of safe-routing.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-24.
-
Advantages and disadvantages of FastEndpoints
There are other approaches to safe routing, like those that use C# Source Generators
Result
Posts with mentions or reviews of Result.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-24.
-
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.
What are some alternatives?
When comparing safe-routing and Result you can also consider the following projects:
Xtz.StronglyTyped - Set of NuGet packages to strongly-type your interfaces (properties, methods, APIs, DB entities, appsettings). Eliminate stringly-typed interfaces. Make compiler your friend, introduce semantics to your code.
FluentResults - A generalised Result object implementation for .NET/C#
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
clean-minimal-api - A project showcasing how you can build a clean Minimal API using FastEndpoints
generator-start - template repository for a roslyn source generator
SmartEnum - A base class for quickly and easily creating strongly typed enum replacements in C#.
Specification - Base class with tests for adding specifications to a DDD model