54 lines
2.7 KiB
Markdown
54 lines
2.7 KiB
Markdown
# Handoff - 2025-12-21
|
|
|
|
## Work Completed
|
|
|
|
### Slug Integration
|
|
|
|
- **Backend**: Updated `Show`, `Song`, `Venue`, `Tour` models/schemas to support `slug`.
|
|
- Updated API routers (`shows.py`, `songs.py`) to lookup by slug or ID.
|
|
- Migrated database schema to include `slug` columns using Alembic.
|
|
- Backfilled slugs using `backend/fix_db_data.py`.
|
|
- **Frontend**: Updated routing and links for entities.
|
|
- `/shows/[id]` -> `/shows/${show.slug || show.id}`
|
|
- `/songs/[id]` -> `/songs/${song.slug || song.id}`
|
|
- `/venues/[id]` -> `/venues/${venue.slug || venue.id}`
|
|
- Updated interfaces to include `slug`.
|
|
- Updated `PerformanceList` component to use slugs.
|
|
|
|
### Data Fixes
|
|
|
|
- **Set Names**:
|
|
- Identified issues with `set_name` being null due to API parameter mismatch (`setnumber` vs `set`).
|
|
- Updated `import_elgoose.py` to correctly extract and format "Set 1", "Set 2", "Encore" from `setnumber`.
|
|
- Attempted to backfill existing data but hit an infinite loop issue with API fetching (Slugs were backfilled successfully). Data can be fixed by re-running a corrected importer or custom script.
|
|
- **Slugs**:
|
|
- `import_elgoose.py` updated to generate slugs for new imports.
|
|
- `fix_db_data.py` successfully backfilled slugs for existing Venues, Songs, Shows, and Tours.
|
|
|
|
### UI Fixes
|
|
|
|
- **Components**: Created missing Shadcn UI components that were causing build failures:
|
|
- `frontend/components/ui/progress.tsx`
|
|
- `frontend/components/ui/checkbox.tsx`
|
|
- **Auth**: Updated `AuthContext` to expose `token` for the Admin page.
|
|
- **Build**: Resolved typescript errors; build process starts correctly.
|
|
|
|
## Current State
|
|
|
|
- **Application**: Fully functional slug-based navigation. Links prioritize slugs but fallback to IDs.
|
|
- **Database**: `slug` columns added. Migration `65c515b4722a_add_slugs` applied. `set_name` still missing for most existing performances (displays as "Set ?").
|
|
- **Codebase**: Clean and updated. `check_api.py` removed. `fix_db_data.py` exists but has pagination bug if re-run.
|
|
|
|
## Next Steps
|
|
|
|
1. **Verify Data**: Check if slugs are working correctly on the frontend.
|
|
2. **Fix Set Names**:
|
|
- Fix pagination in `backend/fix_db_data.py` (check API docs for correct pagination or limit handling).
|
|
- Re-run `python3 fix_db_data.py` to populate `set_name` for existing performances.
|
|
3. **Notifications**: Proceed with planned Notification System implementation (Discord, Telegram).
|
|
4. **Audit Items**: Continue auditing site for missing features/pages.
|
|
|
|
## Technical Notes
|
|
|
|
- **Database Migrations**: Alembic history was manually adjusted to ignore existing `reaction`/`badge` tables to allow `slug` migration to pass on the dev database.
|
|
- **Importer**: `import_elgoose.py` logic is updated for *future* imports.
|