redis-graph-cache 1.0.2 → 1.0.3

package/dist/core/hydration-engine.js

@@ -172,7 +172,22 @@ class HydrationEngine {
             if (context.excludeRelations?.includes(relationName)) {
                 continue;
             }
-            const promise = this.hydrateRelation(relationName, relationDef, normalizedEntity, hydratedEntity, context);
+            // Fork the visited-set per relation branch, synchronously, before any
+            // async work starts. `visitedEntities` tracks the *current path* for
+            // cycle detection (add on enter, delete on exit in `hydrateRecursive`).
+            // Sibling relations are hydrated concurrently (Promise.all below), so if
+            // they shared one Set, one branch's transient in-progress entries would
+            // leak into a sibling's view — making a shared entity referenced by both
+            // a parent and its child collection (a diamond, not a cycle) resolve to a
+            // `$ref` stub instead of the full object. A per-branch clone captures
+            // only the ancestor path, so real cycles down a branch are still caught
+            // while concurrent siblings stay isolated. This mirrors the per-item
+            // clone `batchHydrateEntities` already performs for `many` relations.
+            const branchContext = {
+                ...context,
+                visitedEntities: new Set(context.visitedEntities),
+            };
+            const promise = this.hydrateRelation(relationName, relationDef, normalizedEntity, hydratedEntity, branchContext);
             relationPromises.push(promise);
         }
         // Execute all relationship hydrations in parallel

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "redis-graph-cache",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "A TypeScript-first Redis data layer with schema-driven normalization, relationship management, and graph-based hydration for high-performance Node.js applications.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",