FluentValidation 11.9.0
FluentValidation is validation library for .NET that uses a fluent interface and lambda expressions for building strongly-typed validation rules.
Supporting the project
If you use FluentValidation in a commercial project, please sponsor the project financially. FluentValidation is developed and supported by @JeremySkinner for free in his spare time and financial sponsorship helps keep the project going. You can sponsor the project via either GitHub sponsors or OpenCollective.
Example
With FluentValidation, you can define a class that inherits from AbstractValidator
which contains the rules for a particular class. The example below shows how you could define rules
for a Customer
class, and then how to execute the validator.
using FluentValidation;
public class CustomerValidator: AbstractValidator<Customer> {
public CustomerValidator() {
RuleFor(x => x.Surname).NotEmpty();
RuleFor(x => x.Forename).NotEmpty().WithMessage("Please specify a first name");
RuleFor(x => x.Discount).NotEqual(0).When(x => x.HasDiscount);
RuleFor(x => x.Address).Length(20, 250);
RuleFor(x => x.Postcode).Must(BeAValidPostcode).WithMessage("Please specify a valid postcode");
}
private bool BeAValidPostcode(string postcode) {
// custom postcode validating logic goes here
}
}
var customer = new Customer();
var validator = new CustomerValidator();
// Execute the validator.
ValidationResult results = validator.Validate(customer);
// Inspect any validation failures.
bool success = results.IsValid;
List<ValidationFailure> failures = results.Errors;
Full Documentation
Full documentation can be found at https://docs.fluentvalidation.net
Release Notes and Change Log
Release notes can be found on GitHub.
Showing the top 20 packages that depend on FluentValidation.
Packages | Downloads |
---|---|
FluentValidation.AspNetCore
AspNetCore integration for FluentValidation
|
7 |
FluentValidation.AspNetCore
AspNetCore integration for FluentValidation
|
8 |
FluentValidation.AspNetCore
AspNetCore integration for FluentValidation
|
14 |
FluentValidation.AspNetCore
AspNetCore integration for FluentValidation
|
3,564 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
7 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
8 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
9 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
10 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
11 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
13 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
14 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
350 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
3,564 |
FluentValidation.DependencyInjectionExtensions
Dependency injection extensions for FluentValidation
|
13,993 |
Ocelot
Ocelot is an API Gateway. The project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. reference tokens. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
13 |
Ocelot
This project is aimed at people using .NET running a micro services / service orientated architecture that need a unified point of entry into their system. In particular I want easy integration with IdentityServer reference and bearer tokens. We have been unable to find this in my current workplace without having to write our own Javascript middlewares to handle the IdentityServer reference tokens. We would rather use the IdentityServer code that already exists to do this. Ocelot is a bunch of middlewares in a specific order. Ocelot manipulates the HttpRequest object into a state specified by its configuration until it reaches a request builder middleware where it creates a HttpRequestMessage object which is used to make a request to a downstream service. The middleware that makes the request is the last thing in the Ocelot pipeline. It does not call the next middleware. The response from the downstream service is stored in a per request scoped repository and retrived as the requests goes back up the Ocelot pipeline. There is a piece of middleware that maps the HttpResponseMessage onto the HttpResponse object and that is returned to the client. That is basically it with a bunch of other features.
|
11 |
.NET 5.0
- No dependencies.
.NET 6.0
- No dependencies.
.NET 7.0
- No dependencies.
.NET 8.0
- No dependencies.
.NET Standard 2.0
- System.Threading.Tasks.Extensions (>= 4.5.4)
.NET Standard 2.1
- No dependencies.
Version | Downloads | Last updated |
---|---|---|
11.10.0 | 0 | 09/15/2024 |
11.9.2 | 0 | 06/10/2024 |
11.9.1 | 194 | 05/03/2024 |
11.9.0 | 10 | 04/20/2024 |
11.8.1 | 13 | 05/10/2024 |
11.8.0 | 4 | 05/22/2024 |
11.7.1 | 0 | 08/12/2023 |
11.7.0 | 5 | 05/15/2024 |
11.6.0 | 0 | 07/04/2023 |
11.5.2 | 5 | 06/22/2023 |
11.5.1 | 12 | 04/11/2023 |
11.5.0 | 5 | 05/18/2024 |
11.4.0 | 7 | 05/02/2024 |
11.3.0 | 0 | 11/10/2022 |
11.2.2 | 13,563 | 11/03/2022 |
11.2.1 | 0 | 08/28/2022 |
11.2.0 | 0 | 08/08/2022 |
11.1.1 | 0 | 08/06/2022 |
11.1.0 | 3,539 | 07/25/2022 |
11.0.3 | 0 | 06/10/2022 |
11.0.2 | 0 | 05/27/2022 |
11.0.1 | 0 | 05/07/2022 |
11.0.0 | 4 | 05/06/2024 |
10.3.1 | 0 | 08/19/2021 |
10.2.1 | 5 | 05/11/2022 |
10.2.0 | 0 | 05/28/2021 |
9.5.4 | 0 | 04/05/2021 |
9.4.0 | 5 | 05/26/2024 |
9.3.0-preview3 | 5 | 05/25/2024 |
9.3.0-preview2 | 5 | 05/25/2024 |
9.2.2 | 5 | 06/01/2024 |
9.2.1 | 0 | 09/19/2020 |
9.1.2 | 0 | 08/12/2020 |
9.1.1 | 0 | 08/08/2020 |
9.1.0 | 0 | 08/08/2020 |
9.0.1 | 0 | 07/14/2020 |
9.0.0-preview5 | 5 | 05/25/2024 |
9.0.0-preview3 | 8 | 05/25/2024 |
9.0.0-preview2 | 3 | 05/25/2024 |
9.0.0-preview1 | 5 | 05/25/2024 |
8.6.3 | 0 | 08/28/2020 |
8.6.2 | 7 | 11/04/2022 |
8.6.1 | 0 | 12/28/2019 |
8.5.0 | 5 | 05/16/2024 |
8.5.0-preview5 | 3 | 05/25/2024 |
8.5.0-preview3 | 6 | 05/25/2024 |
8.5.0-preview1 | 5 | 05/25/2024 |
8.3.0 | 0 | 04/24/2019 |
8.2.1 | 6 | 05/10/2022 |
8.1.2 | 0 | 12/18/2018 |
8.0.100 | 0 | 09/04/2018 |
8.0.0-rc1 | 0 | 07/24/2018 |
8.0.0-preview3 | 4 | 05/25/2024 |
7.6.104 | 4 | 05/23/2024 |
7.6.0-preview1 | 5 | 05/25/2024 |
7.5.1 | 0 | 03/11/2018 |
7.4.0 | 6 | 05/15/2024 |
7.3.2 | 4 | 05/30/2024 |
7.3.1 | 0 | 12/13/2017 |
7.3.0-beta2 | 0 | 11/20/2017 |
7.2.1 | 4 | 05/23/2024 |
7.2.0 | 0 | 10/05/2017 |
7.2.0-beta2 | 0 | 08/22/2017 |
7.1.0-beta1 | 0 | 06/24/2017 |
7.0.1 | 9 | 05/11/2022 |
7.0.0 | 0 | 05/19/2017 |
7.0.0-beta2 | 0 | 04/17/2017 |
7.0.0-beta1 | 0 | 04/07/2017 |
6.4.1 | 3 | 05/31/2024 |
6.4.1-beta1 | 0 | 03/13/2017 |
6.4.0-rc2 | 0 | 01/30/2017 |
6.4.0-rc1 | 0 | 01/30/2017 |
6.4.0-beta8 | 0 | 10/31/2016 |
6.4.0-beta7 | 0 | 10/28/2016 |
6.4.0-beta4 | 0 | 10/21/2016 |
6.4.0-beta3 | 0 | 07/04/2016 |
6.4.0-beta1 | 0 | 06/28/2016 |
6.2.1-beta1 | 0 | 02/24/2016 |
6.1.0 | 5 | 05/14/2024 |
6.0.1 | 0 | 01/05/2016 |
6.0.0 | 0 | 12/22/2015 |
5.6.2 | 5 | 05/13/2024 |
5.6.1 | 8 | 05/03/2024 |
5.3.0 | 0 | 05/27/2014 |
4.0.0.1 | 7 | 05/20/2024 |
3.0.0.1 | 4 | 05/23/2024 |
3.0.0 | 0 | 06/25/2011 |
2.0.0 | 7 | 05/08/2022 |