Add frontend TypeScript types for game data models

Define Game, Route, Pokemon, RouteEncounter, Encounter, and NuzlockeRun
types mirroring the backend schema, with EncounterStatus and RunStatus
discriminated union types.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Julian Tabel
2026-02-05 13:34:21 +01:00
parent d94364d6ce
commit 08c05f2a2f
3 changed files with 73 additions and 8 deletions

View File

@@ -0,0 +1,62 @@
export interface Game {
id: number
name: string
slug: string
generation: number
region: string
boxArtUrl: string | null
releaseYear: number | null
}
export interface Route {
id: number
name: string
gameId: number
order: number
}
export interface Pokemon {
id: number
nationalDex: number
name: string
types: string[]
spriteUrl: string | null
}
export interface RouteEncounter {
id: number
routeId: number
pokemonId: number
encounterMethod: string
encounterRate: number
}
export type EncounterStatus = 'caught' | 'fainted' | 'missed'
export interface Encounter {
id: number
runId: number
routeId: number
pokemonId: number
nickname: string | null
status: EncounterStatus
catchLevel: number | null
faintLevel: number | null
caughtAt: string
}
export type RunStatus = 'active' | 'completed' | 'failed'
export interface NuzlockeRun {
id: number
gameId: number
name: string
status: RunStatus
rules: NuzlockeRules
startedAt: string
completedAt: string | null
}
// Re-export for convenience
import type { NuzlockeRules } from './rules'
export type { NuzlockeRules }

View File

@@ -1 +1,2 @@
export * from './game'
export * from './rules'