fix memory render

[ishaanxgupta]

No description provided.

[claude]

Claude finished @ishaanxgupta's task in 46s —— View job

---

Review Complete

• Analyzing PR changes
• Checking for bugs and security issues
• Submitting review

---

Overview: Simplifies edge source/target node lookup by reusing the already-computed srcId/tgtId variables instead of redundant type checking, along with a patch version bump.

Issues found: None — this looks good to ship.

The change at renderer.ts:247-248 correctly leverages the existing type handling at lines 227-228 where srcId and tgtId are extracted. The old code duplicated this type check unnecessarily:

// Old - redundant type check
const src = typeof edge.source === "string" ? nodeMap.get(edge.source) : edge.source
// New - clean reuse
const src = nodeMap.get(srcId)

The new approach is actually safer — it always looks up nodes from nodeMap, ensuring consistent node references rather than potentially using stale objects stored directly in edge data.

Score: 10/10

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
✅ Deployment successful! View logs	supermemory-mcp	85caa11	Jun 14 2026, 06:14 PM

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	supermemory-app	85caa11	Commit Preview URL Branch Preview URL	Jun 14 2026, 06:14 PM

[claude]

Overview: Simplifies edge source/target node lookup by reusing the already-computed srcId/tgtId variables instead of redundant type checking.

Issues found: None — this looks good to ship.

The change correctly leverages the existing type handling at lines 227-228 where srcId and tgtId are extracted. The old code duplicated this type check unnecessarily. The new code is cleaner and always looks up nodes from nodeMap, which is actually safer as it ensures consistent node references rather than potentially using stale objects stored directly in edge data.

Score: 10/10