@venizia/ignis-docs 0.2.0 → 0.2.1-1

package/content/references/base/providers.md

@@ -10,7 +10,7 @@ lastUpdated: 2026-03-15
 Providers implement the Factory pattern in IGNIS, allowing you to create and configure instances dynamically at runtime based on configuration or context. Unlike services that contain business logic, providers are factories that produce values, instances, or functions.
 
 **Files:**
-- `packages/core/src/base/providers/base.ts`
+- `packages/core-server/src/base/providers/base.ts`
 
 ## Prerequisites
 
@@ -229,7 +229,7 @@ export class LoggerProvider extends BaseProvider<ILogger> {
 }
 ```
 
-Register the provider with `.toProvider()` - consumers then `get()` the **produced value**, not the provider instance (the container instantiates the provider and calls `value(container)` for you):
+Register the provider with `.toProvider()`. Consumers then `get()` the **produced value**, not the provider instance - the container instantiates the provider and calls `value(container)` for you:
 
 ```typescript
 // In your application (e.g. preConfigure)
@@ -327,7 +327,7 @@ graph TD
 
 1. **Registered via `.toProvider()`**: Providers are bound explicitly (`bind({ key }).toProvider(MyProvider)`), not auto-scanned
 2. **`value()` Called by the Container**: `container.get({ key })` instantiates the provider and calls `value(container)` - consumers receive the produced value, never the provider instance
-3. **Singleton Scope Caches the Produced Value**: With `.setScope(BindingScopes.SINGLETON)`, the container caches the result of `value()` and returns it on subsequent `get()` calls; with the default transient scope, `value()` runs on every `get()`
+3. **Singleton Scope Caches the Produced Value**: With `.setScope(BindingScopes.SINGLETON)`, the container caches the result of `value()` and returns it on subsequent `get()` calls. With the default transient scope, `value()` runs on every `get()`
 4. **Factory vs Instance**: Providers can return:
    - Direct instances (created each time `value()` is called)
    - Factory functions (deferred creation)
@@ -350,7 +350,7 @@ app.bind({ key: 'providers.Database' }).toProvider(DatabaseProvider);
 
 ### Example 1: Mail Transport Provider
 
-From `packages/core/src/components/mail/providers/mail-transporter.provider.ts`:
+From `packages/core-server/src/components/mail/providers/mail-transporter.provider.ts`:
 
 ```typescript
 export type TGetMailTransportFn = (options: TMailOptions) => IMailTransport;
@@ -419,7 +419,7 @@ this.application.bind({ key: MailKeys.MAIL_TRANSPORT_INSTANCE }).toValue(mailTra
 
 ### Example 2: Queue Executor Provider
 
-From `packages/core/src/components/mail/providers/mail-queue-executor.provider.ts`:
+From `packages/core-server/src/components/mail/providers/mail-queue-executor.provider.ts`:
 
 ```typescript
 export type TGetMailQueueExecutorFn = (config: IMailQueueExecutorConfig) => IMailQueueExecutor;
@@ -472,7 +472,7 @@ export class MailQueueExecutorProvider extends BaseProvider<TGetMailQueueExecuto
 Providers can also produce middleware. `RequestSpyMiddleware` is a real-world example that implements `IProvider<MiddlewareHandler>` directly (extending `BaseHelper`, not `BaseProvider`):
 
 ```typescript
-// From packages/core/src/base/middlewares/request-spy/request-spy.middleware.ts
+// From packages/core-server/src/base/middlewares/request-spy/request-spy.middleware.ts
 export class RequestSpyMiddleware extends BaseHelper implements IProvider<MiddlewareHandler> {
   static readonly REQUEST_ID_KEY = 'requestId';
 
@@ -509,7 +509,7 @@ export class RequestSpyMiddleware extends BaseHelper implements IProvider<Middle
 
 See [Middlewares](./middlewares.md) for the full implementation (IP resolution, body-parsing rules, and production log redaction).
 
-Note that `RequestSpyMiddleware.value()` does not accept a `container` parameter -- the `IProvider<T>` interface defines `value(container: Container): T`, but implementations may ignore the parameter when they don't need container access. In practice, `RequestSpyMiddleware` is registered via `RequestTrackerComponent`, which binds it as a provider in the DI container and resolves it automatically.
+Note that `RequestSpyMiddleware.value()` does not accept a `container` parameter. The `IProvider<T>` interface defines `value(container: Container): T`, but implementations may ignore the parameter when they don't need container access. In practice, `RequestSpyMiddleware` is registered via `RequestTrackerComponent`, which binds it as a provider in the DI container and resolves it automatically.
 
 
 ## Common Patterns
@@ -545,7 +545,7 @@ export class S3StorageProvider extends BaseProvider<S3Storage> {
 
 ### Pattern 2: Lazy Singleton
 
-Create instance only once, lazily (or simply bind with `.setScope(BindingScopes.SINGLETON)` and let the container cache the produced value):
+Create instance only once, lazily (or bind with `.setScope(BindingScopes.SINGLETON)` and let the container cache the produced value):
 
 ```typescript
 export class DatabaseConnectionProvider extends BaseProvider<DatabaseConnection> {