From 15d2e0c682694fd12f73fc1c156ef6307d0260e1 Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Thu, 30 Jul 2026 21:56:02 -0400 Subject: [PATCH] =?UTF-8?q?fix(design-systems):=20declare=20tokenRationale?= =?UTF-8?q?=20=E2=80=94=20the=20ref=20its=20usages=20referenced?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Broke the typecheck on 0f80b79. The scripted edit that added the three `tokenRationale` usages and the one that declared the ref were separate replacements, and only the declaration's anchor was wrong — so three usages landed against a name that did not exist. The declaration's replacement had no assertion on it while its neighbours did. An anchor that matches nothing is a no-op, and a no-op looks exactly like success. --- frontend/src/views/DesignSystemsView.vue | 2 ++ 1 file changed, 2 insertions(+) diff --git a/frontend/src/views/DesignSystemsView.vue b/frontend/src/views/DesignSystemsView.vue index f62ece5..12725c1 100644 --- a/frontend/src/views/DesignSystemsView.vue +++ b/frontend/src/views/DesignSystemsView.vue @@ -254,6 +254,8 @@ const showAddToken = ref(false); const tokenName = ref(""); const tokenGroup = ref(""); const tokenPurpose = ref(""); +/** Why the token is this value — a different question from what it is for. */ +const tokenRationale = ref(""); /** Mode/value pairs, edited as a list so a token can carry any number of modes. */ const tokenModes = ref<{ mode: string; value: string }[]>([{ mode: "base", value: "" }]); /** Literals this token should be written instead of, comma-separated in the