From ffe54a59a36149a9d1d7c3d7138a7fc009e630c0 Mon Sep 17 00:00:00 2001 From: Zuz666 <109312+Zuz666@users.noreply.github.com> Date: Thu, 23 Jul 2026 08:04:41 +0500 Subject: [PATCH] fix(skills): make skippedReason switch exhaustive (#9594) The type-aware switch-exhaustiveness lint rule requires explicit cases for 'current', 'duplicate', and undefined; they fall through to the existing generic skipped message, so behavior is unchanged. Co-authored-by: Yuris Auzins --- .../src/components/skills/skill-freshness-group.tsx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/renderer/src/components/skills/skill-freshness-group.tsx b/src/renderer/src/components/skills/skill-freshness-group.tsx index c6dac9647..514acad74 100644 --- a/src/renderer/src/components/skills/skill-freshness-group.tsx +++ b/src/renderer/src/components/skills/skill-freshness-group.tsx @@ -134,7 +134,11 @@ function skippedReason(locations: readonly SkillLocationRow[]): string { 'auto.components.skills.SkillFreshnessRow.skippedReasonBrokenLink', 'This copy is a shortcut to something that no longer exists, so Orca left it out — you can safely delete it.' ) - default: + // Why: 'current'/'duplicate' are non-blocking chips, and an empty priority + // list is possible; all fall through to the generic skipped message. + case 'current': + case 'duplicate': + case undefined: return translate( 'auto.components.skills.SkillFreshnessRow.cantUpdateReason', 'Orca left this skill out of the update command.'