From 0ea991b62851e4b996c7a607c08e0575ebc9a3ec Mon Sep 17 00:00:00 2001 From: Bryan Frimin Date: Thu, 7 May 2026 12:58:46 +0200 Subject: [PATCH] Drop redundant @deleteRecord on campaigns list mutation @deleteEdge already removes the deleted campaign from the connection on the list view, so the extra @deleteRecord was redundant. The detail page mutation still uses @deleteRecord since it has no connection to delete from. Signed-off-by: Bryan Frimin --- .../access-reviews/campaigns/AccessReviewCampaignsTab.tsx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/apps/console/src/pages/organizations/access-reviews/campaigns/AccessReviewCampaignsTab.tsx b/apps/console/src/pages/organizations/access-reviews/campaigns/AccessReviewCampaignsTab.tsx index 76c511d6b..0ab51981a 100644 --- a/apps/console/src/pages/organizations/access-reviews/campaigns/AccessReviewCampaignsTab.tsx +++ b/apps/console/src/pages/organizations/access-reviews/campaigns/AccessReviewCampaignsTab.tsx @@ -91,9 +91,7 @@ const deleteCampaignMutation = graphql` $connections: [ID!]! ) { deleteAccessReviewCampaign(input: $input) { - deletedAccessReviewCampaignId - @deleteEdge(connections: $connections) - @deleteRecord + deletedAccessReviewCampaignId @deleteEdge(connections: $connections) } } `;