testing ADR - architectural decisions

docs/adr/0003-standardized-input-validation-using-middleware.md

@@ -8,24 +8,24 @@
 
 Our Express route handlers currently perform manual validation of request parameters, queries, and bodies. This involves repetitive boilerplate code using `parseInt`, `isNaN`, and type checks like `Array.isArray`. This approach has several disadvantages:
 
-1.  **Code Duplication**: The same validation logic (e.g., checking for a valid integer ID) is repeated across many different routes.
-2.  **Cluttered Business Logic**: Route handlers are cluttered with validation code, obscuring their primary business logic.
-3.  **Inconsistent Error Messages**: Manual validation can lead to inconsistent error messages for similar validation failures across the API.
-4.  **Error-Prone**: It is easy to forget a validation check, leading to unexpected data types being passed to service and repository layers, which could cause runtime errors.
+1. **Code Duplication**: The same validation logic (e.g., checking for a valid integer ID) is repeated across many different routes.
+2. **Cluttered Business Logic**: Route handlers are cluttered with validation code, obscuring their primary business logic.
+3. **Inconsistent Error Messages**: Manual validation can lead to inconsistent error messages for similar validation failures across the API.
+4. **Error-Prone**: It is easy to forget a validation check, leading to unexpected data types being passed to service and repository layers, which could cause runtime errors.
 
 ## Decision
 
 We will adopt a schema-based approach for input validation using the `zod` library and a custom Express middleware.
 
-1.  **Adopt `zod` for Schema Definition**: We will use `zod` to define clear, type-safe schemas for the `params`, `query`, and `body` of each API request. `zod` provides powerful and declarative validation rules and automatically infers TypeScript types.
+1. **Adopt `zod` for Schema Definition**: We will use `zod` to define clear, type-safe schemas for the `params`, `query`, and `body` of each API request. `zod` provides powerful and declarative validation rules and automatically infers TypeScript types.
 
-2.  **Create a Reusable Validation Middleware**: A generic `validateRequest(schema)` middleware will be created. This middleware will take a `zod` schema, parse the incoming request against it, and handle success and error cases.
-    *   On successful validation, the parsed and typed data will be attached to the `req` object (e.g., `req.body` will be replaced with the parsed body), and `next()` will be called.
-    *   On validation failure, the middleware will call `next()` with a custom `ValidationError` containing a structured list of issues, which `ADR-001`'s `errorHandler` can then format into a user-friendly `400 Bad Request` response.
+2. **Create a Reusable Validation Middleware**: A generic `validateRequest(schema)` middleware will be created. This middleware will take a `zod` schema, parse the incoming request against it, and handle success and error cases.
+    * On successful validation, the parsed and typed data will be attached to the `req` object (e.g., `req.body` will be replaced with the parsed body), and `next()` will be called.
+    * On validation failure, the middleware will call `next()` with a custom `ValidationError` containing a structured list of issues, which `ADR-001`'s `errorHandler` can then format into a user-friendly `400 Bad Request` response.
 
-3.  **Refactor Routes**: All route handlers will be refactored to use this new middleware, removing all manual validation logic.
+3. **Refactor Routes**: All route handlers will be refactored to use this new middleware, removing all manual validation logic.
 
-### Example Usage:
+### Example Usage
 
 ```typescript
 // In flyer.routes.ts
@@ -67,4 +67,4 @@ router.get('/:id', validateRequest(getFlyerSchema), async (req, res, next) => {
 
 **New Dependency**: Introduces `zod` as a new project dependency.
 **Learning Curve**: Developers need to learn the `zod` schema definition syntax.
-**Refactoring Effort**: Requires a one-time effort to create schemas and refactor all existing routes to use the `validateRequest` middleware.
+**Refactoring Effort**: Requires a one-time effort to create schemas and refactor all existing routes to use the `validateRequest` middleware.