2026-02-11 17:00:16 +01:00
---
# nuzlocke-tracker-m86o
title: Add naming scheme selection to run configuration
2026-02-11 21:51:35 +01:00
status: completed
2026-02-11 17:00:16 +01:00
type: task
priority: normal
created_at: 2026-02-11T15:56:44Z
2026-02-11 21:51:35 +01:00
updated_at: 2026-02-11T20:37:00Z
2026-02-11 17:00:16 +01:00
parent: nuzlocke-tracker-igl3
blocking:
- nuzlocke-tracker-bi4e
---
Allow users to select a naming scheme (category) for their Nuzlocke run.
## Requirements
2026-02-11 21:36:50 +01:00
- Add a `naming_scheme` column to the NuzlockeRun model (nullable string — user may not want auto-naming)
2026-02-11 17:00:16 +01:00
- Provide a dropdown/selector in run creation and run settings where the user can pick a category
2026-02-11 21:36:50 +01:00
- List available categories dynamically by querying a backend endpoint that reads the dictionary file
2026-02-11 17:00:16 +01:00
- Allow changing the naming scheme mid-run
2026-02-11 21:36:50 +01:00
## Implementation Notes
- **Storage**: Dedicated nullable `naming_scheme` column on `NuzlockeRun` (not in the `rules` JSONB). This is a first-class run setting.
- **Migration**: Add an Alembic migration for the new column.
- **API**: Add/update the run creation and update endpoints to accept `namingScheme` .
- **Categories endpoint**: Add a GET endpoint that returns the list of available category names from the dictionary file, so the frontend can populate the dropdown.
2026-02-11 17:00:16 +01:00
## Checklist
2026-02-11 21:36:50 +01:00
- [x] Add `naming_scheme` nullable column to NuzlockeRun model
- [x] Create Alembic migration for the new column
- [x] Update run Pydantic schemas to include `namingScheme`
- [x] Update run creation and update endpoints to persist the naming scheme
- [x] Add GET endpoint to list available naming categories from the dictionary
- [x] Add naming scheme selector to run creation UI
- [x] Add naming scheme selector to run settings UI