From 779fd76def6136031cf3a77b4a599cfce40d799f Mon Sep 17 00:00:00 2001
From: Adnaan <badr.adnaan@gmail.com>
Date: Sun, 25 Jan 2026 12:51:35 +0100
Subject: [PATCH] feat: support auto-generated _k keys in range item matching

Check for the auto-generated _k field first in getItemKey() to support
range items that don't have explicit key attributes in the template.

This works in conjunction with the server-side change that injects
_k fields into range items when no explicit key attribute is defined.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---
 state/tree-renderer.ts | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/state/tree-renderer.ts b/state/tree-renderer.ts
index 4564727..9ccf706 100644
--- a/state/tree-renderer.ts
+++ b/state/tree-renderer.ts
@@ -792,6 +792,11 @@ export class TreeRenderer {
     statics: any[],
     statePath?: string
   ): string | null {
+    // First check for auto-generated _k field (always takes priority)
+    if (item._k && typeof item._k === "string") {
+      return item._k;
+    }
+
     if (!statePath || !this.rangeIdKeys[statePath]) {
       return null;
     }