FluentValidation: our changes to an open source project
A popular .NET library for writing strongly typed validation rules.
- Language
- C#
- GitHub stars
- 9,756
- Project site
- fluentvalidation.net
The change merged into FluentValidation
Range validation rejects an inverted range even when the comparer returns any negative number, not only -1.
- Pull request #2370merged on 9 September 2026
What it taught us
The .NET comparison contract only promises the sign of the result. Code that checks for exactly -1 works until the first comparer that returns -2.
C# and .NET
Our projects in this technology, their screens and when we choose it.
Other projects with our changes: C# and .NET
7 projects in this technology have our merged changes. The bar is the repository's stars, next to it the number of our changes. Each row leads to the project's page.
- ILSpy3 merged changes26,543
- OpenRA1 merged change17,537
- Polly1 merged change14,242
- FluentValidationthis page, 1 merged change9,756
- Serilog1 merged change8,049
- NLog2 merged changes6,547
- Markdig2 merged changes5,341
FluentValidation among all our changes
Day by day from 5 September 2026 to 11 October 2026. A column is every change merged that day, the accent is the changes in FluentValidation.
- Changes in FluentValidation
- Changes in other projects
1 merged change in FluentValidation
Merged on 9 September 2026.
On the same day
Changes of ours were also merged into: Monolog, stats.
Questions about our changes to FluentValidation
Where these changes come from, who merged them and whether we can fix something in your library.
Read next
More about this work and the other projects with our changes.
Using FluentValidation in your project?
If something in it does not work, we fix it at the source and leave a workaround until the release. We reply within an hour.