Builtin Model State Validatio
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 505
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
maybe I'm missing something, but do I really have to validate the incoming model in every controller-method? AFAIK dotnet core 2.1 introduced automatic validation OOTB as a behaviour of the middleware. Is something like this available for OData as well?
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
The issue names no files or tests. Start by comparing ASP.NET Core 2.1 automatic model validation with the OData controller pipeline and determine whether equivalent behavior is supported. Done means establishing the supported behavior or a clearly scoped implementation, with validation behavior covered appropriately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100