ASP.NET developers struggle to run async model validation cleanly
ASP.NET developers need model checks that call asynchronous services, but the validation APIs described in these reports are synchronous. Blocking on async work can be risky, while custom async validation paths make it harder to reuse existing logic and library features. A TypeScript class-transformer request points to a related need to await promises during data transformation, though the clearest opportunity is in ASP.NET.
For ASP.NET developers and validation-library maintainers. Mentioned from Jan 2021 to May 2022 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 7.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
The validation actually needs to check the value from the other underlying services which only provides an async method. This means we still have to either write the code to block the thread which is not quite sure if it will cause a deadlock in some cases
FluentValidation's validators allow either sync or async execution, but because ASP.NET's validation APIs are only synchronous, we are unable to offer the library's full feature-set to ASP.NET users, and warn them that if their validator contains async code then it'll end up be run synchronously
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks