Seed the database with Pokemon game data for 5 games (FireRed, LeafGreen, Emerald, HeartGold, SoulSilver) using pokebase. Includes Alembic migrations for route unique constraints and encounter level ranges, a two-phase seed system (offline fetch to JSON, then idempotent upserts), and Dockerfile updates for the seed runner. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
26 lines
1.0 KiB
Markdown
26 lines
1.0 KiB
Markdown
---
|
|
# nuzlocke-tracker-j28y
|
|
title: Curate route ordering to match game progression
|
|
status: todo
|
|
type: task
|
|
created_at: 2026-02-05T13:37:39Z
|
|
updated_at: 2026-02-05T13:37:39Z
|
|
parent: nuzlocke-tracker-f5ob
|
|
---
|
|
|
|
Routes are currently in alphabetical order from PokeAPI. Update the order field in each game's JSON seed file to reflect actual game progression (e.g., Pallet Town → Route 1 → Viridian City → Route 2 → ...).
|
|
|
|
## Details
|
|
- 646 routes total across 5 games
|
|
- FireRed and LeafGreen share the same route progression (Kanto)
|
|
- HeartGold and SoulSilver share the same route progression (Johto + Kanto)
|
|
- Emerald has its own progression (Hoenn)
|
|
- So effectively 3 unique orderings to define
|
|
- After updating JSON files, re-run the seed: `podman compose exec -e PYTHONUNBUFFERED=1 -w /app/src api python -m app.seeds`
|
|
|
|
## Files
|
|
- `backend/src/app/seeds/data/firered.json`
|
|
- `backend/src/app/seeds/data/leafgreen.json`
|
|
- `backend/src/app/seeds/data/emerald.json`
|
|
- `backend/src/app/seeds/data/heartgold.json`
|
|
- `backend/src/app/seeds/data/soulsilver.json` |