@venizia/ignis-docs 0.0.1 → 0.0.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@venizia/ignis-docs",
-  "version": "0.0.1",
+  "version": "0.0.3",
   "description": "Documentation and MCP Server for Ignis Framework",
   "keywords": [
     "ignis",
@@ -111,7 +111,7 @@
     "@braintree/sanitize-url": "^7.1.1",
     "@types/bun": "^1.3.4",
     "@types/glob": "^8.1.0",
-    "@venizia/dev-configs": "^0.0.2",
+    "@venizia/dev-configs": "^0.0.4",
     "eslint": "^9.36.0",
     "glob": "^10.4.2",
     "prettier": "^3.6.2",

package/wiki/changelogs/2025-12-26-nested-relations-and-generics.md

@@ -0,0 +1,86 @@
+---
+title: Nested Relations & Generic Types
+description: Added support for deep nested inclusions and generic return types in repositories
+---
+
+# Changelog - 2025-12-26
+
+## Nested Relations Support & Generic Repository Types
+
+This update introduces support for deeply nested relation queries in repositories and enables stronger type safety via generic return types.
+
+## Overview
+
+- **Nested Inclusions**: `include` filters now work recursively to any depth.
+- **Generic Repository Methods**: `find<R>`, `findOne<R>`, etc. now support custom return types.
+- **DrizzleFilterBuilder Decoupling**: Decoupled filter builder from MetadataRegistry for cleaner architecture.
+
+## New Features
+
+### Nested Relations Support
+
+**File:** `packages/core/src/base/repositories/operators/filter.ts`
+
+**Problem:** Previously, the `DrizzleFilterBuilder` could only resolve relations for the root entity. Nested includes (e.g., `include: [{ relation: 'a', scope: { include: [{ relation: 'b' }] } }]`) failed because it didn't know the schema of relation 'a'.
+
+**Solution:** The builder now accepts a `relationResolver` function (injected from the Repository) which allows it to dynamically lookup schemas and relations for any entity during recursive traversal.
+
+```typescript
+// Now works recursively!
+const result = await repo.findOne({
+  filter: {
+    include: [{
+      relation: 'orders',
+      scope: {
+        include: [{ relation: 'items' }] // Level 2
+      }
+    }]
+  }
+});
+```
+
+### Generic Repository Methods
+
+**File:** `packages/core/src/base/repositories/common/types.ts`
+
+**Problem:** Repository methods like `findOne` were hardcoded to return the base `DataObject`. When using `include`, the return type didn't reflect the added relations, forcing users to use `as any` or unsafe casts.
+
+**Solution:** All read and write methods now accept a generic type parameter `<R>` which defaults to the entity's schema but can be overridden.
+
+```typescript
+// Define expected shape
+type UserWithPosts = User & { posts: Post[] };
+
+// Type-safe call
+const user = await userRepo.findOne<UserWithPosts>({
+  filter: { include: [{ relation: 'posts' }] }
+});
+
+// TypeScript knows 'posts' exists!
+console.log(user?.posts.length);
+```
+
+**Benefits:**
+- Stronger type safety in application code.
+- Reduces need for `as any` casting.
+- Better IDE auto-completion.
+
+## Files Changed
+
+### Core Package (`packages/core`)
+
+| File | Changes |
+|------|---------|
+| `src/base/repositories/common/types.ts` | Added generic `<R>` to all repository interface methods |
+| `src/base/repositories/core/base.ts` | Implemented `getRelationResolver` and updated abstract signatures |
+| `src/base/repositories/core/readable.ts` | Updated `find`, `findOne`, `findById` to support generics |
+| `src/base/repositories/core/persistable.ts` | Updated `create`, `update`, `delete` methods to support generics |
+| `src/base/repositories/operators/filter.ts` | Added `relationResolver` support for recursive includes |
+
+## Migration Guide
+
+### No Breaking Changes
+
+This update is fully backward compatible.
+- Existing calls to repository methods will continue to work (using the default `DataObject` return type).
+- The new generic type parameter is optional.

package/wiki/changelogs/2025-12-26-transaction-support.md

@@ -0,0 +1,57 @@
+---
+title: Transaction Support
+description: Explicit transaction support for atomic operations across repositories
+---
+
+# Changelog - 2025-12-26
+
+## Transaction Support
+
+Added explicit transaction support to the repository layer, enabling atomic operations across multiple services and repositories.
+
+## Overview
+
+- **Explicit Transactions**: `beginTransaction()` method on repositories.
+- **Isolation Levels**: Support for `READ COMMITTED`, `REPEATABLE READ`, and `SERIALIZABLE`.
+- **Pass-through Context**: Transaction objects can be passed via `options`.
+
+## New Features
+
+### Repository Transactions
+
+**File:** `packages/core/src/base/repositories/core/base.ts`
+
+**Problem:** Previously, transactions relied on Drizzle's callback API, which made it difficult to share a transaction context across different services or decoupled components.
+
+**Solution:** Introduced explicit `ITransaction` objects managed by the repository/datasource.
+
+```typescript
+const tx = await repo.beginTransaction();
+
+try {
+  await repo.create({ data: {...}, options: { transaction: tx } });
+  await otherRepo.create({ data: {...}, options: { transaction: tx } });
+  
+  await tx.commit();
+} catch (err) {
+  await tx.rollback();
+}
+```
+
+## Files Changed
+
+### Core Package (`packages/core`)
+
+| File | Changes |
+|------|---------|
+| `src/base/repositories/core/base.ts` | Added `beginTransaction` and transaction handling logic |
+| `src/base/repositories/core/readable.ts` | Updated read methods to respect transaction context |
+| `src/base/repositories/core/persistable.ts` | Updated write methods to respect transaction context |
+| `src/base/datasources/common/types.ts` | Added `ITransaction`, `ITransactionOptions`, and `IsolationLevels` |
+| `src/base/datasources/base.ts` | Implemented `beginTransaction` on `BaseDataSource` |
+
+## Migration Guide
+
+### No Breaking Changes
+
+This is an additive feature. Existing code using standard CRUD methods will continue to work without modification (using implicit auto-commit transactions).

package/wiki/changelogs/index.md

@@ -11,12 +11,14 @@ This section tracks the history of significant changes, refactors, and updates t
 
 | Feature | Description | Priority |
 |---------|-------------|----------|
-| [Transaction Support](./planned-transaction-support) | Loopback 4-style explicit transaction objects with isolation levels | Future |
+| [Schema Migrator](./planned-schema-migrator) | LoopBack 4-style auto schema migration without Drizzle Kit | High |
 
 ## Recent Changes
 
 | Date | Title | Type |
 |------|-------|------|
+| 2025-12-26 | [Transaction Support](./2025-12-26-transaction-support) | Enhancement |
+| 2025-12-26 | [Nested Relations & Generic Types](./2025-12-26-nested-relations-and-generics) | Enhancement |
 | 2025-12-18 | [Performance Optimizations](./2025-12-18-performance-optimizations) | Enhancement |
 | 2025-12-18 | [Repository Validation & Security](./2025-12-18-repository-validation-security) | Breaking Change, Security |
 | 2025-12-17 | [Inversion of Control Refactor](./2025-12-17-refactor) | Refactor |