From de838600dd2e123e4c8d2f86bd06fbaa8995f504 Mon Sep 17 00:00:00 2001 From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com> Date: Thu, 9 Apr 2026 18:22:00 +0000 Subject: [PATCH] fix: filter release targets by search query client-side The search bar was accepting input but never applying it as a filter. The query value is passed to the API which doesn't support text filtering, so add client-side filtering by resource name and identifier instead. Co-authored-by: Aditya Choudhari --- .../ws/deployments/page.$deploymentId.release-targets.tsx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/apps/web/app/routes/ws/deployments/page.$deploymentId.release-targets.tsx b/apps/web/app/routes/ws/deployments/page.$deploymentId.release-targets.tsx index 1ed68859e..e27afe483 100644 --- a/apps/web/app/routes/ws/deployments/page.$deploymentId.release-targets.tsx +++ b/apps/web/app/routes/ws/deployments/page.$deploymentId.release-targets.tsx @@ -166,7 +166,12 @@ export default function ReleaseTargetsPage() { jobStatus == null || camelCase(rt.latestJob?.status ?? "") === jobStatus; const isMatchingVersion = version === "all" || rt.currentVersion?.id === version; - return isMatchingJobStatus && isMatchingVersion; + const q = searchDebounced.toLowerCase(); + const isMatchingSearch = + q === "" || + rt.resource.name.toLowerCase().includes(q) || + rt.resource.identifier.toLowerCase().includes(q); + return isMatchingJobStatus && isMatchingVersion && isMatchingSearch; }); const groupByEnvironmentId = _.groupBy(