000658b4cd
The DB accumulated stale routes from previous imports with different naming (e.g. "Route 1" alongside "Alola Route 1"). These were exported back to JSON, causing duplicate entries with conflicting order values. Removed 597 stale routes across 17 game files and re-sorted all 22 game files to match the canonical progression in route_order.json. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
17 lines
798 B
Markdown
17 lines
798 B
Markdown
---
|
|
# nuzlocke-tracker-qgfv
|
|
title: Clean up stale duplicate routes in game JSON files
|
|
status: completed
|
|
type: task
|
|
priority: normal
|
|
created_at: 2026-02-13T07:24:40Z
|
|
updated_at: 2026-02-13T07:25:56Z
|
|
---
|
|
|
|
Game JSON files (especially Gen 7) have stale route entries from a previous import that used different naming. The seeder upserted without cleaning up, so the DB accumulated both old (e.g. 'Route 1') and new (e.g. 'Alola Route 1') entries. Then --export dumped both to JSON, creating duplicates with conflicting order values.
|
|
|
|
## Checklist
|
|
- [ ] Identify all affected game JSON files
|
|
- [ ] Remove stale/duplicate route entries (the ones not in route_order.json)
|
|
- [ ] Reassign sequential order values to fix the gaps
|
|
- [ ] Verify no data loss (the kept routes should have all the encounter data) |