| Age | Commit message (Collapse) | Author | Lines |
|
Parametric resource routes cause a React Router prod build error
(commonjs--resolver server-only module conflict). Merged the GET?id=
and PATCH logic into the existing api-bands.tsx and api-artists.tsx
instead of creating separate :uuid route files.
- GET /api/bands?id=UUID → band detail with links/members
- PATCH /api/bands → partial update (append_links, append_members)
- Same pattern for /api/artists
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Removing default component export makes these resource routes,
so React Router returns the Response directly instead of wrapping in HTML SSR.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Replace band_artists + member_periods with a single members table
(id, band_id, artist_id, role, since, until, note, order_index).
Each row represents one membership period, so rejoining artists
get multiple rows. Existing band_artists data is auto-migrated on
startup. Export format bumped to version 3.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
|
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|