fix: Rate limit tab now correctly filters to only rate-limited requests

The rate limit filter was looking up a property filter by label, which failed
when the Helicone-Rate-Limit-Status property hadn't been used yet. This caused
the filter node to be an empty object ({}) that matched all requests instead
of only rate-limited ones.

Fixed by building the filter node directly using the known property structure.
Use empty object {} when not filtering (valid FilterNode type) instead of "all"
string which causes backend validation errors.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: 2 people

web/components/templates/requests/useRequestsPageV2.tsx

@@ -72,18 +72,20 @@ const useRequestsPageV2 = (
     };
   }
 
-  const rateLimitFilterMapIndex = filterMap.findIndex(
-    (filter: any) => filter.label?.trim() === "Helicone-Rate-Limit-Status",
-  );
-
-  let rateLimitFilterNode: FilterNode = {} as FilterLeaf;
-  if (rateLimited && rateLimitFilterMapIndex !== -1) {
-    rateLimitFilterNode = filterUITreeToFilterNode(filterMap, {
-      filterMapIdx: rateLimitFilterMapIndex,
-      operatorIdx: 0,
-      value: "rate_limited",
-    });
-  }
+  // Build rate limit filter directly instead of looking it up in filterMap
+  // This ensures it works even if the property hasn't been used yet
+  // Use empty object {} to match all when not filtering by rate limited
+  const rateLimitFilterNode: FilterNode = rateLimited
+    ? {
+        request_response_rmt: {
+          properties: {
+            "Helicone-Rate-Limit-Status": {
+              equals: "rate_limited",
+            },
+          },
+        },
+      }
+    : {};
 
   // sort the model by name
   models?.data?.sort((a, b) => a.model.localeCompare(b.model));