@venizia/ignis-docs 0.0.5-0 → 0.0.6-0

package/wiki/guides/tutorials/testing.md

@@ -703,7 +703,7 @@ class CreateAndUpdateAndDeleteHandler extends TestCaseHandler {
 
 ## Next Steps
 
-- [Testing Reference](../../references/helpers/testing.md) - Complete API documentation
+- [Testing Reference](../../references/helpers/testing/) - Complete API documentation
 - [Best Practices](../../best-practices/code-style-standards/) - Code quality standards
 - [Troubleshooting](../../best-practices/troubleshooting-tips.md) - Common issues
 

package/wiki/references/base/bootstrapping.md

@@ -773,8 +773,6 @@ await app.boot();
 ```
 
 
----
-
 ## See Also
 
 - **Related References:**

package/wiki/references/base/components.md

@@ -589,10 +589,10 @@ export * from './controller';
   - [Dependency Injection](/guides/core-concepts/dependency-injection) - Component bindings
 
 - **Built-in Components:**
-  - [Authentication Component](/references/components/authentication) - JWT authentication
+  - [Authentication Component](/references/components/authentication/) - JWT authentication
   - [Health Check Component](/references/components/health-check) - Health endpoints
   - [Swagger Component](/references/components/swagger) - API documentation
-  - [Socket.IO Component](/references/components/socket-io) - WebSocket support
+  - [Socket.IO Component](/references/components/socket-io/) - WebSocket support
 
 - **Best Practices:**
   - [Architectural Patterns](/best-practices/architectural-patterns) - Component design patterns

package/wiki/references/base/controllers.md

@@ -632,7 +632,6 @@ export class ConfigurationController extends _Controller {
 }
 ```
 
----
 
 ## See Also
 

package/wiki/references/base/datasources.md

@@ -341,7 +341,7 @@ try {
 }
 ```
 
-> **Note:** For most use cases, prefer using `repository.beginTransaction()` which provides a higher-level API. See [Repositories Reference](./repositories/.md#transactions) for details.
+> **Note:** For most use cases, prefer using `repository.beginTransaction()` which provides a higher-level API. See [Repositories Reference](./repositories/#transactions) for details.
 
 This architecture ensures that datasources are configured consistently and that the fully-initialized Drizzle connector, aware of all schemas and relations, is available to repositories for querying.
 

package/wiki/references/base/dependency-injection.md

@@ -201,7 +201,7 @@ class UserController {
   - [Providers](/references/base/providers) - Factory pattern for dynamic injection
 
 - **References:**
-  - [Inversion Helper](/references/helpers/inversion) - DI container utilities
+  - [Inversion Helper](/references/helpers/inversion/) - DI container utilities
   - [Bootstrapping API](/references/base/bootstrapping) - Auto-discovery and DI
   - [Glossary](/guides/reference/glossary#dependency-injection-di) - DI concepts explained
 

package/wiki/references/base/filter-system/quick-reference.md

@@ -22,7 +22,6 @@ Complete single-page reference for all IGNIS filter operators. For detailed expl
 
 **See:** [Comparison Operators Guide](./comparison-operators.md)
 
----
 
 ## Range Operators
 
@@ -33,7 +32,6 @@ Complete single-page reference for all IGNIS filter operators. For detailed expl
 
 **See:** [Range Operators Guide](./range-operators.md)
 
----
 
 ## List Operators
 
@@ -44,7 +42,6 @@ Complete single-page reference for all IGNIS filter operators. For detailed expl
 
 **See:** [List Operators Guide](./list-operators.md)
 
----
 
 ## Pattern Matching Operators
 
@@ -65,7 +62,6 @@ Complete single-page reference for all IGNIS filter operators. For detailed expl
 
 **See:** [Pattern Matching Guide](./pattern-matching.md)
 
----
 
 ## Null Check Operators
 
@@ -83,7 +79,6 @@ Complete single-page reference for all IGNIS filter operators. For detailed expl
 
 **See:** [Null Operators Guide](./null-operators.md)
 
----
 
 ## Logical Operators
 
@@ -106,7 +101,6 @@ Complete single-page reference for all IGNIS filter operators. For detailed expl
 
 **See:** [Logical Operators Guide](./logical-operators.md)
 
----
 
 ## PostgreSQL Array Operators
 
@@ -122,7 +116,6 @@ These operators work with PostgreSQL array columns (`varchar[]`, `text[]`, `inte
 
 **See:** [Array Operators Guide](./array-operators.md)
 
----
 
 ## JSON/JSONB Operators (PostgreSQL)
 
@@ -166,7 +159,6 @@ All comparison operators work with JSON path queries:
 
 **See:** [JSON Filtering Guide](./json-filtering.md)
 
----
 
 ## Fields, Ordering & Pagination
 
@@ -211,7 +203,6 @@ const users = await userRepo.find({
 
 **See:** [Fields, Ordering & Pagination Guide](./fields-order-pagination.md)
 
----
 
 ## Default Filters
 
@@ -250,7 +241,6 @@ await userRepo.find({
 
 **See:** [Default Filter Guide](./default-filter.md)
 
----
 
 ## Common Filter Patterns
 
@@ -314,7 +304,6 @@ await userRepo.find({
 }
 ```
 
----
 
 ## Operator Precedence
 
@@ -339,7 +328,6 @@ Use explicit parentheses (via nested `and`/`or`) for clarity:
 }
 ```
 
----
 
 ## Type Safety
 
@@ -371,7 +359,6 @@ await userRepo.find({
 });
 ```
 
----
 
 ## Performance Tips
 
@@ -407,7 +394,6 @@ await userRepo.find({
    }
    ```
 
----
 
 ## See Also
 

package/wiki/references/base/middlewares.md

@@ -7,7 +7,7 @@ lastUpdated: 2026-01-03
 
 # Middlewares Reference
 
-IGNIS provides a collection of built-in middlewares for common application needs including error handling, request logging, request normalization, and favicon serving.
+IGNIS provides a collection of built-in middlewares for common application needs including error handling, request logging, and favicon serving.
 
 **Files:**
 - `packages/core/src/base/middlewares/*.ts`
@@ -24,16 +24,14 @@ IGNIS provides a collection of built-in middlewares for common application needs
 |------------|---------|-------------|
 | `appErrorHandler` | Catches and formats application errors | `logger` |
 | `notFoundHandler` | Handles 404 Not Found responses | `logger` |
-| `requestNormalize` | Pre-parses JSON request bodies | None |
-| `RequestSpyMiddleware` | Logs request lifecycle and timing | None |
+| `RequestSpyMiddleware` | Logs request lifecycle, timing, and parses request body | None |
 | `emojiFavicon` | Serves an emoji as favicon | `icon` |
 
 ## Table of Contents
 
 - [Error Handler (`appErrorHandler`)](#error-handler-apporerrorhandler)
 - [Not Found Handler (`notFoundHandler`)](#not-found-handler-notfoundhandler)
-- [Request Normalizer (`requestNormalize`)](#request-normalizer-requestnormalize)
-- [Request Spy (Debug)](#request-spy-debug)
+- [Request Spy (`RequestSpyMiddleware`)](#request-spy-requestspymiddleware)
 - [Emoji Favicon](#emoji-favicon)
 - [Creating Custom Middleware](#creating-custom-middleware)
 - [Middleware Order & Priority](#middleware-order--priority)
@@ -189,7 +187,6 @@ async getUser(c: TRouteContext) {
 }
 ```
 
----
 
 ### Not Found Handler (`notFoundHandler`)
 
@@ -235,67 +232,24 @@ app.notFound(notFoundHandler({
 
 **Returns:** `NotFoundHandler` - Hono not found handler function
 
----
-
-### Request Normalizer (`requestNormalize`)
-
-Pre-parses JSON request bodies to ensure consistent request handling and prevent common parsing issues.
-
-**File:** `packages/core/src/base/middlewares/request-normalize.middleware.ts`
 
-#### How It Works
-
-1. **Skip for GET/OPTIONS**: No normalization for read-only requests
-2. **Check Content-Length**: Skip if no body is present (`Content-Length: 0`)
-3. **Check Content-Type**: Only process `application/json` requests
-4. **Pre-parse JSON**: Calls `context.req.json()` to cache the parsed body
-
-#### Benefits
+### Request Spy (`RequestSpyMiddleware`)
 
-- Prevents multiple body parsing attempts
-- Ensures body is available for all subsequent middleware/handlers
-- Catches JSON parsing errors early in the request lifecycle
-
-#### Usage
-
-```typescript
-import { requestNormalize } from '@venizia/ignis';
-
-const app = new IgnisApplication({
-  // ...
-});
-
-// Register as early middleware
-app.use(requestNormalize());
-```
-
-:::tip Why Pre-parse?
-Hono's request body can only be read once. This middleware ensures the body is parsed and cached early, making it available to all downstream handlers.
-:::
-
-#### API Reference
-
-##### `requestNormalize()`
-
-**Parameters:** None
-
-**Returns:** `MiddlewareHandler` - Hono middleware function
-
----
-
-### Request Spy (Debug)
-
-Logs detailed information about each request including timing, IP address, method, path, and query parameters.
+Logs detailed information about each request including timing, IP address, method, path, query parameters, and request body. Also handles request body parsing for JSON, form data, and text content types.
 
 **File:** `packages/core/src/base/middlewares/request-spy.middleware.ts`
 
 #### Features
 
-- Request lifecycle logging (START/DONE)
+- Request lifecycle logging (incoming/outgoing)
 - Performance timing tracking
 - IP address extraction (supports `x-real-ip` and `x-forwarded-for` headers)
 - Request ID tracking
-- Query and body parameter logging
+- Query and body parameter logging (body only logged in non-production)
+- **Request body parsing**: Automatically parses and caches request bodies:
+  - `application/json` → `req.json()`
+  - `multipart/form-data`, `application/x-www-form-urlencoded` → `req.parseBody()`
+  - Other content types (text, html, xml) → `req.text()`
 
 #### Usage
 
@@ -363,7 +317,6 @@ async example(c: TRouteContext) {
 Request spy logs every request detail. Consider disabling or reducing verbosity in production environments with high traffic.
 :::
 
----
 
 ### Emoji Favicon
 
@@ -416,7 +369,6 @@ app.use(emojiFavicon({ icon: '🌟' })); // Star
 SVG favicons are supported in all modern browsers. Fallback to a traditional `.ico` file if you need to support legacy browsers.
 :::
 
----
 
 ## Creating Custom Middleware
 
@@ -494,7 +446,6 @@ const myMiddleware = app.get(MyMiddleware);
 app.use(myMiddleware.value());
 ```
 
----
 
 ## Middleware Order & Priority
 
@@ -511,49 +462,44 @@ app.use(cors());
 // 2. Request ID generation
 app.use(requestId());
 
-// 3. Request spy/logging
+// 3. Request spy/logging (also handles body parsing)
 const requestSpy = new RequestSpyMiddleware();
 app.use(requestSpy.value());
 
-// 4. Request normalization
-app.use(requestNormalize());
-
-// 5. Security middleware (helmet, etc.)
+// 4. Security middleware (helmet, etc.)
 app.use(helmet());
 
-// 6. Rate limiting
+// 5. Rate limiting
 app.use(rateLimit());
 
-// 7. Authentication
+// 6. Authentication
 app.use('/api/*', authenticate());
 
-// 8. Favicon (can be early or late)
+// 7. Favicon (can be early or late)
 app.use(emojiFavicon({ icon: '🚀' }));
 
-// 9. Application routes
+// 8. Application routes
 app.mountControllers();
 
-// 10. Error handler (LAST in chain)
+// 9. Error handler (LAST in chain)
 app.onError(appErrorHandler({ logger: app.logger }));
 
-// 11. Not found handler (AFTER error handler)
+// 10. Not found handler (AFTER error handler)
 app.notFound(notFoundHandler({ logger: app.logger }));
 ```
 
 ### Key Principles
 
 1. **Request ID First**: Generate request ID before logging
-2. **Logging Early**: Log requests before normalization/parsing
-3. **Normalization Before Business Logic**: Parse bodies before they're needed
-4. **Security Middleware Before Routes**: Protect routes with security checks
-5. **Error Handler Last**: Catch all errors from previous middleware
-6. **404 Handler After Error Handler**: Ensure unhandled routes return 404
+2. **Request Spy Early**: Log and parse request bodies before business logic
+3. **Security Middleware Before Routes**: Protect routes with security checks
+4. **Error Handler Last**: Catch all errors from previous middleware
+5. **404 Handler After Error Handler**: Ensure unhandled routes return 404
 
 :::warning Order Matters
 Placing error handler before routes will prevent it from catching route errors. Always register error handlers last.
 :::
 
----
 
 ## Common Patterns
 
@@ -584,14 +530,13 @@ app.use('/api/public/*', rateLimitMiddleware());
 const apiMiddleware = (): MiddlewareHandler => {
   return createMiddleware(async (context, next) => {
     // Run multiple middleware in sequence
-    await requestNormalize()(context, async () => {
+    await rateLimit()(context, async () => {
       await authenticate()(context, next);
     });
   });
 };
 ```
 
----
 
 ## Performance Considerations
 
@@ -616,7 +561,6 @@ Error handlers log every error. For high error rates, consider:
 - Error aggregation services (Sentry, Rollbar)
 - Rate-limited logging
 
----
 
 ## See Also
 

package/wiki/references/base/providers.md

@@ -49,7 +49,6 @@ A **Provider** is a class that implements the Factory pattern, responsible for c
 - **Multi-Tenant**: Provide tenant-specific instances
 - **Feature Flags**: Enable/disable features at runtime
 
----
 
 ## BaseProvider Class
 
@@ -99,7 +98,6 @@ The `value` method is where you implement your factory logic.
 - Create and configure instances based on logic
 - Return factories for deferred instantiation
 
----
 
 ## Provider vs Service
 
@@ -185,7 +183,6 @@ class OrderService extends BaseService {
 - **Need to implement business logic?** → Use a Service
 :::
 
----
 
 ## Creating Custom Providers
 
@@ -297,7 +294,6 @@ export class DatabaseProvider extends BaseProvider<Database> {
 }
 ```
 
----
 
 ## Provider Lifecycle
 
@@ -354,7 +350,6 @@ export class FactoryDatabaseProvider extends BaseProvider<Database> {
 }
 ```
 
----
 
 ## Real-World Examples
 
@@ -498,7 +493,6 @@ const requestSpy = new RequestSpyMiddleware();
 app.use(requestSpy.value());
 ```
 
----
 
 ## Common Patterns
 
@@ -589,7 +583,6 @@ export class CacheProvider extends BaseProvider<ICache> {
 }
 ```
 
----
 
 ## Common Pitfalls
 
@@ -664,7 +657,6 @@ value(container: Container): IMailTransport {
 }
 ```
 
----
 
 ## Performance Considerations
 
@@ -710,7 +702,6 @@ export class ConfigProvider extends BaseProvider<Config> {
 }
 ```
 
----
 
 ## See Also
 

package/wiki/references/base/services.md

@@ -102,7 +102,6 @@ export class UserService extends BaseService {
 
 By adhering to this pattern, you keep your code organized, testable, and maintainable. You can easily test `UserService` by providing a mock `UserRepository` without needing a real database connection.
 
----
 
 ## See Also