DamianEdwards / DamianEdwards/MiniValidation
Figure out how to react to .NET 11 support for async validation
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 390
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
.NET 11 is getting support for async validation in System.ComponentModel.DataAnnotations: https://www.reddit.com/r/dotnet/comments/1ukw9ny/async_model_validation_is_finally_coming_in_net_11/
A few things to consider:
- this project already defines an
IAsyncValidatableObjectinterface which will cause naming conflicts with the new interface introduced in .NET 11 - the
ValidatorandValidationAttributetypes are getting new methods to support async validation which this project should call into as appropriate when running on .NET 11
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing IAsyncValidatableObject interface and the Validator and ValidationAttribute types, then compare them with the async validation APIs planned for .NET 11. Define how the project should avoid naming conflicts and use the new framework methods while preserving supported targets; done means the compatibility approach is agreed and captured in implementation work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100