Monorepo DTO & Input Validation Layer

[inteee]

Context: Across all these APIs (Auth, Clinics, Users), we need strict runtime validation to prevent bad data from hitting our controllers or database.
Location: apps/api/src/middlewares/validate.middleware.ts
Requirements:

1. Implement a generic Zod validation middleware: validateRequest(zodSchema).
2. Apply Zod schemas to all Phase 1 routes (POST /auth/login, POST /clinics/register, POST /users).
3. Return beautifully formatted 400 Bad Request errors detailing exactly which fields failed.
   Acceptance Criteria:

• Missing passwords or invalid emails are caught before the controller logic runs.
• The middleware is strongly typed, inferring req.body types for the controllers.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[romeoscript]

@romeoscript has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I'd like to take this on. Generic Zod middleware with strong TypeScript inference and clean error formatting is something I've implemented before in Node/Express backends.
I'll implement validateRequest(zodSchema) in validate.middleware.ts, apply schemas to all three Phase 1 routes, and return well-structured 400 responses with per-field error details. PR ready in 1 day.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @romeoscript to this issue.