aspnet-api-versioning
FluentValidation
Our great sponsors
aspnet-api-versioning | FluentValidation | |
---|---|---|
12 | 20 | |
2,979 | 8,753 | |
1.6% | 1.0% | |
8.7 | 7.9 | |
5 days ago | about 1 month 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.
aspnet-api-versioning
-
Web API Versioning - 'apiVersion' constraint
Here is a code example
- Best way to version a CQRS-oriented REST api
- How do you handle API versioning? And naming.
- Is this a common way to version REST apis
-
Angular, ASP.NET core web api, and DTOs
- The DTOs on the server should generally not change without warning. A deprecation cycle should ideally be in place so consumers can keep up over time and front end development doesn't have to be lock-step with the services the consume. Ideally some period of time between service v1 being deprecated and service v2 being required to allow consumers to react ( in this case, you're the consumer, so be kind to yourself ). Deets: https://github.com/dotnet/aspnet-api-versioning
-
8 quick tips to improve your .NET API
This API versioning can be parameterized with some options, including the default version or even how the versioning will be done, whether by URL, header or media type. For more details, you can access the official documentation.
-
Entity Changes and API Versioning - Looking for best practice
https://github.com/dotnet/aspnet-api-versioning/tree/master/samples/aspnetcore/BasicSample/Controllers something like this
-
API version control (route name error)
Could you not achieve what you want by using ASP.NET API versioning - there's a by namespace example here
-
.NET Core — API Versioning
A lista completa pode ser vista aqui: https://github.com/microsoft/aspnet-api-versioning/wiki/Version-Format
-
Web API in 5 Hours (2021)
You don't have to use attributes. You can use conventions. See here.
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?
api-guidelines - Microsoft REST API Guidelines
Guard - A high-performance, extensible argument validation library.
CleanArchitecture - Clean Architecture Solution Template for ASP.NET Core
CsvHelper - Library to help reading and writing CSV files
Swashbuckle.AspNetCore - Swagger tools for documenting API's built on ASP.NET Core
ReactJS.NET - .NET library for JSX compilation and server-side rendering of React components
ApiVersioningSwagger - Api Versioning Swagger example
Mediator.Net - A simple mediator for .Net for sending command, publishing event and request response with pipelines supported
ASP.NET Boilerplate - ASP.NET Boilerplate - Web Application Framework
MediatR - Simple, unambitious mediator implementation in .NET
Versioning.NET - A dotnet tool that automatically increments versions in csproj files based on git commit hints.
Enums.NET - Enums.NET is a high-performance type-safe .NET enum utility library