1aa67665ff
Set up tools/import-pokedb/ with CLI, JSON loader, and output models. Replaces the Go/PokeAPI approach with local PokeDB.org JSON processing. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
30 lines
1.3 KiB
Markdown
30 lines
1.3 KiB
Markdown
---
|
|
# nuzlocke-tracker-dqyb
|
|
title: Set up Python tool scaffold
|
|
status: in-progress
|
|
type: task
|
|
priority: normal
|
|
created_at: 2026-02-11T08:42:58Z
|
|
updated_at: 2026-02-11T08:44:03Z
|
|
parent: nuzlocke-tracker-bs05
|
|
blocking:
|
|
- nuzlocke-tracker-zno2
|
|
---
|
|
|
|
Set up the standalone Python tool project in `tools/import-pokedb/`.
|
|
|
|
## Checklist
|
|
|
|
- [x] Create `tools/import-pokedb/` directory structure
|
|
- [x] Set up `pyproject.toml` with dependencies (just stdlib should suffice for JSON processing, maybe `click` for CLI)
|
|
- [x] Create CLI entry point (`__main__.py` or similar) that accepts:
|
|
- Path to directory containing PokeDB JSON export files
|
|
- Target output directory (default: `backend/src/app/seeds/data/`)
|
|
- Optional: specific game version to generate (default: all)
|
|
- [x] Load and parse all PokeDB JSON files: `encounters.json`, `locations.json`, `location_areas.json`, `encounter_methods.json`, `versions.json`, `pokemon_forms.json`
|
|
- [x] Basic validation that all expected files are present and parseable
|
|
|
|
## Notes
|
|
- Keep it as a standalone tool, not part of the backend
|
|
- The PokeDB JSON files are downloaded manually from https://pokedb.org/data-export — no need to automate the download
|
|
- Model the CLI similarly to how `tools/fetch-pokeapi/` works (cd into dir, run the tool) |