Skip to content

OpenAPI type generation pipeline #30

Description

@guidefari

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

  • Script or tooling to generate TypeScript types from Spotify OpenAPI spec
  • Clear separation between generated and handwritten code
  • Regeneration doesn't destroy Effect-specific schemas or facades

Related

PRD #9 — user stories 14, 15, 37


Migrated from guidefari/spotify-effect#44

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions