FastEndpoints
FluentValidation
Our great sponsors
FastEndpoints | FluentValidation | |
---|---|---|
15 | 20 | |
3,904 | 8,772 | |
6.4% | 1.2% | |
9.7 | 7.9 | |
4 days ago | 6 days ago | |
C# | C# | |
MIT License | Apache License 2.0 |
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.
FastEndpoints
-
Choosing Between Controllers and Minimal API for .NET APIs
Bonus Time! In addition to the Microsoft-supported methods above, many community frameworks exist for building APIs with .NET. FastEndpoints is an option I found recently that seems very promising. With performance benchmarks that put them on par with Minimal API, they are firmly ahead of Controller-based APIs.
-
How do you structure large Minimal API Projects?
Have you had a look at FastEndpoints yet? Any thoughts?
-
Microsoft launches new app store for Windows – from React to Shoelace, Lit, Vite
And yet, all Microsoft's demos for the upcoming changes for Blazor in .NET 8 (like SSR) has been a public facing recipe site (e.g. https://www.youtube.com/watch?v=QD2-DwuOfKM). I'd say this is a very similar use case as the Microsoft Store.
I love .NET and ASP.NET Core, but I use it purely for backend. And even there, I use 3rd party libraries like Fast Endpoints (https://fast-endpoints.com/). Microsoft keeps bringing in new technologies and effectively abandoning the ones that fall out of favour (look at the progression from MVC -> Razor Pages -> Blazor). I do not blame the Microsoft Store team for not trusting the .NET team to not simply abandon Blazor as well somewhere down the line and instead opt for other technologies for the front-end.
-
Idea validation | low-code API factory
I also find a very similar framework in .NET "Fast Endpoints"
-
Easiest way to build the fastest REST API in C# and .NET 7 using CQRS
I gave it a go and I was impressed how easy and fast it was to set it all up. Since I'm not a big fan of REPR pattern almost all my projects are using CQRS pattern with a help of MediatR ](https://github.com/jbogard/MediatR) I immediately started going over something similar that Fast Endpoints offer which is a command bus.
- Should I utilize C#/.NET Core, or go with Typescript for a React front end?
-
Which 'part' of dotnet should I learn for backend web dev?
Ive personally been using FastEndpoints which is a community built thing on top of minimal apis - https://fast-endpoints.com/
-
Reprise - a micro-framework that brings the REPR pattern into Minimal APIs
I've just started to use a similar thing, and it's so much better than controllers - https://fast-endpoints.com/
-
Easiest/Standard way to implement a simple HTTP REST API?
Sort of minimal but check out FastEndpoint. https://fast-endpoints.com/
FluentValidation
-
Easiest way to build the fastest REST API in C# and .NET 7 using CQRS
Here is an example of Command handler with built-in Fluent Validation and fire and forget style:
-
8 quick tips to improve your .NET API
There is an RFC called Problem Details (RFC7807) that standardizes how an error in an API should be responded to for the client. If you use Fluent validation, you may have noticed that the response is within this pattern.
- [Parte 2] CQRS y MediatR: Validando con FluentValidation
-
Building REST APIs In .Net 6 The Easy Way!
here we're defining the input validation requirements using fluent validation rules. let's see what happens when the user input doesn't meet the above criteria. execute the same request in swagger with the following incorrect json content:
-
How to properly sanitise & check POST data from REST API? Which libraries can you suggest? best ways nowadays in 2022
I remember FluentValidation being a nice library for this type of stuff.
-
Improving Anemic Models
Literally the code example in the front page: https://fluentvalidation.net/
-
BREAKING!! NPM package ‘ua-parser-js’ with more than 7M weekly download is compromised
https://www.nuget.org/packages/Newtonsoft.Json/ https://www.nuget.org/packages/AutoMapper/ https://www.nuget.org/packages/Dapper/ https://www.nuget.org/packages/FluentValidation/ https://www.nuget.org/packages/FluentAssertions/ https://www.nuget.org/packages/NUnit/ https://www.nuget.org/packages/xunit/ https://www.nuget.org/packages/YamlDotNet/ https://www.nuget.org/packages/Moq/ That is simply not true. Mature c# projects purposely maintain no downstream dependencies and is they do, it's to a major reputable lib. See for yourself - these are staple third party packages commonly used. Anything dependency starting with System or NETStandard is Microsoft maintained.
- ASP.NET Core 6: Minimal APIs y Carter
-
GraphQL mutation union erros (6a) with Hotchocolate GraphQL Server
FluentValidator for validating and authorising certain fields.
-
Request Validation for Asp.NET API with Fluent Validation
Now that we know the importance of providing users with enough information about their requests and how it was processed, let’s focus on how we can configure our API to help us do that.One aspect of such meaningful experience is Request Validation (400 Error Range). For that purpose I am using a library called Fluent Validation.
What are some alternatives?
ApiEndpoints - A project for supporting API Endpoints in ASP.NET Core web applications.
Guard - A high-performance, extensible argument validation library.
Carter - Carter is framework that is a thin layer of extension methods and functionality over ASP.NET Core allowing code to be more explicit and most importantly more enjoyable.
CsvHelper - Library to help reading and writing CSV files
Refit - The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface.
ReactJS.NET - .NET library for JSX compilation and server-side rendering of React components
SqlClient - Microsoft.Data.SqlClient provides database connectivity to SQL Server for .NET applications.
Mediator.Net - A simple mediator for .Net for sending command, publishing event and request response with pipelines supported
RestSharp - Simple REST and HTTP API Client for .NET
MediatR - Simple, unambitious mediator implementation in .NET
NetCoreServer - Ultra fast and low latency asynchronous socket server & client C# .NET Core library with support TCP, SSL, UDP, HTTP, HTTPS, WebSocket protocols and 10K connections problem solution
Enums.NET - Enums.NET is a high-performance type-safe .NET enum utility library