chore: add nuget package description
This also removes the description from the package readme. The desciption of the package is shown on nuget.org in the list view and if no package readme is defined on the detail view of a package version. Since we provide a package readme we do not need the description shown twice.
This commit is contained in:
parent
2572bd3695
commit
ef734ad02e
6 changed files with 8 additions and 13 deletions
|
|
@ -1,6 +1,3 @@
|
|||
Request.Validation is a lightweight validation library for C#, built around composable validators, fluent rules, and
|
||||
structured validation results.
|
||||
|
||||
## Features
|
||||
|
||||
- **Composable validators:** Build validators by inheriting from `Validator<T>` and defining rules with `RuleFor` and
|
||||
|
|
@ -56,7 +53,7 @@ public sealed class CreateUserRequestValidator : Validator<CreateUserRequest>
|
|||
.Length(2, 100)
|
||||
.WithCode("NAME_INVALID");
|
||||
|
||||
RuleFor(request => request.Age)
|
||||
RuleFor(request => request.Age)
|
||||
.Between(18, 120);
|
||||
|
||||
RuleFor(request => request.Address)
|
||||
|
|
@ -82,4 +79,4 @@ foreach (var problem in validation.Problems)
|
|||
```
|
||||
|
||||
The resulting `Problem` entries include full property paths like `Address.Street` and `Tags[0]`, making it easy to
|
||||
surface validation errors back to callers or APIs.
|
||||
surface validation errors back to callers or APIs.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue