From 0cf60bb123b9e4840b035ee1e78bfc754b813e44 Mon Sep 17 00:00:00 2001 From: Timo Saikkonen Date: Wed, 8 Jul 2026 11:52:15 +0300 Subject: [PATCH] fix(front): respect muted persons/repos for gitlab notifications Operator precedence made the filter evaluate as `(!muted && gitlabOnlyInvolved) ? !notInvolved : true`, so muted persons, bots and repos were never excluded from the list that drives push notifications. Muting a person/bot therefore had no effect on GitLab. Wrap the ternary so the mute check always applies, matching the GitHub path. Co-authored-by: Cursor --- src/routes/(app)/dashboard/+page.svelte | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/routes/(app)/dashboard/+page.svelte b/src/routes/(app)/dashboard/+page.svelte index 419d9be6..9805b51a 100644 --- a/src/routes/(app)/dashboard/+page.svelte +++ b/src/routes/(app)/dashboard/+page.svelte @@ -316,10 +316,10 @@ ]; } - return newNotifications.filter((item) => - !notificationIsMuted(item, persons, repos) && $settings.gitlabOnlyInvolved - ? !item.notInvolved - : true + return newNotifications.filter( + (item) => + !notificationIsMuted(item, persons, repos) && + ($settings.gitlabOnlyInvolved ? !item.notInvolved : true) ); }