Summary
Set up automated type generation from Spotify's OpenAPI spec instead of hand-maintaining types.
Context
PRD implementation decisions: "Generated Spotify OpenAPI types will be the canonical contract source" and "Generated artifacts and handwritten modules will be kept clearly separated."
Current state: all types in model/SpotifyObjects.ts and model/SpotifyObjectSchemas.ts are hand-written. This works but creates drift risk as Spotify's API evolves.
Acceptance criteria
Related
PRD #9 — user stories 14, 15, 37
Migrated from guidefari/spotify-effect#44
Summary
Set up automated type generation from Spotify's OpenAPI spec instead of hand-maintaining types.
Context
PRD implementation decisions: "Generated Spotify OpenAPI types will be the canonical contract source" and "Generated artifacts and handwritten modules will be kept clearly separated."
Current state: all types in
model/SpotifyObjects.tsandmodel/SpotifyObjectSchemas.tsare hand-written. This works but creates drift risk as Spotify's API evolves.Acceptance criteria
Related
PRD #9 — user stories 14, 15, 37
Migrated from guidefari/spotify-effect#44