cuttle-cards/cuttle

Part of #1399. Summary Nine components are already on <script setup> and still carry exactly one type error each. They do not need migrating — they need a type annotation. Small, uniform, and a good first issue. Why these exist Four of them (AwardCard, BaseLineChart, ThreeDialog, StatsLeaderboardCell) were migrated in #1416–#1419 against the original wording of #1412, which wrongly promised the migration would clear their type errors. It did not. Measured: main was at 420 frontend errors before those four PRs and is at 420 after. The migrations were correct and worth doing on AGENTS.md grounds, but the errors are untyped props, which <script setup> does not touch. #1412 has been corrected. Scope Errors Lines File 1 41 src/components/OauthLink.vue 1 51 src/routes/game/components/dialogs/components/RulesDialog.vue 1 78 src/routes/game/components/dialogs/components/FiveDialog.vue 1 80 src/components/AwardCard.vue 1 99 src/routes/game/components/dialogs/components/gameOv

Part of #1399. One of six store issues. Follows the conventions set in #1422. Summary Convert src/stores/gameHistory.js to TypeScript. 90 lines, already on the setup syntax. Mostly derived state, so the typing is concentrated in one place. Scope One piece of real state and nine computeds derived from it: const gameStates = ref([]); // <- the only thing that needs declaring const isSpectating = computed(() => route.name === ROUTE_NAME_SPECTATE); const currentGameStateIndex = computed(() => { ... }); const currentGameState = computed(() => { ... }); const priorGameStates = computed(() => { ... }); const log = computed(() => { ... }); const showPlaybackControls = computed(() => { ... }); const canGoToPreviousState = computed(() => { ... }); const canGoToNextState = computed(() => { ... }); const clipUrl = computed(() => { ... }); Because the computeds derive from gameStates, typing that one ref propagates to all nine for free

Part of #1399. One of six store issues. Follows the conventions set in #1422. Summary Convert src/stores/myGames.js to TypeScript. 67 lines, already on the setup syntax. Scope const games = ref([]); // <- empty literal: element type never pinned const loading = ref(false); const hasMore = ref(true); const totalCount = ref(0); async function loadMyGames(options = {}) { ... } function resetGames() { ... } Two things need stating that inference cannot recover: games is ref([]), so its element type is unknown to the checker and every consumer of myGamesStore.games is unchecked. Declare the game shape and use ref<MyGame[]>([]). loadMyGames(options = {}) — the options bag is implicit any. Read the call sites and the API response it consumes, then declare both. The game shape likely overlaps what gameList and game hold. If so, put the shared interface somewhere reusable (src/types/ is a reasonable home) rather than duplicating it — but do not over-abstract on the first p

Part of #1399. One of six store issues. Summary Convert src/stores/snackbar.js to TypeScript. 38 lines — the smallest store, already on the setup syntax, and a good place to establish the conventions the other five will follow. Scope const showSnackbar = ref(false); // -> ref<boolean> (already inferred correctly) const snackMessage = ref(''); // -> ref<string> (already inferred correctly) const snackColor = ref(''); // -> candidate for a union type const snackTimeout = ref(0); // -> ref<number> (already inferred correctly) function alert(message, color = 'error', timeout = 5000) { ... } function clear() { ... } The ref initialisers here are non-empty literals, so inference already works. The real gain is the function parameters, which are currently implicit any: type SnackColor = 'error' | 'success' | 'info' | 'warning'; function alert(message: string, color: SnackColor = 'error', timeout = 5000) { ... } Check the actual call sites before fixing the SnackCol

NoteStatus update 2026-10-07. Four of the six are merged (#1416 AwardCard, #1417 BaseLineChart, #1418 ThreeDialog, #1419 StatsLeaderboardCell), SpectatorListMenu is in flight as #1415, and only FourDialog.vue is unclaimed. The migrations did not change the error count. Measured: main was at 420 frontend errors before those four PRs and is at 420 after — confirming the correction below. Their type errors are untyped props and are now tracked in #1428, which types them with <script setup lang="ts">. ImportantCorrected 2026-10-06. This issue originally claimed migrating these six files would clear their type errors. That was wrong — measured with vue-tsc, only 1 of the 6 has a migration-fixable error. The other five are untyped props, which <script setup> does not touch. Summary Convert the remaining small Options API components to <script setup lang="ts">. The value here is AGENTS.md compliance, not type-error reduction — only FourDialog.vue has an error the migration actually fi