@intern make a new table and service for drum layouts. like maps, they are just a record that is backed by an S3 asset. columns should include id, name, description, an image path (like album art URL), and a jsonb "layout_format" column containing additional metadata.
the json column should be parsed by a Zod schema when going in and out of the db.
that schema for now should only contain a single property, "drumCounts", which itself is a record from drum name in camelCase to the number of that drum type in the kit layout.
do not implement the parsing and validation of the drum layout file upon upload - just have a TODO there for me to implement.
use the same upload flow and logic as the maps upload endpoints. if possible, refactor it to be reusable to this as well.
@intern make a new table and service for drum layouts. like maps, they are just a record that is backed by an S3 asset. columns should include id, name, description, an image path (like album art URL), and a jsonb "layout_format" column containing additional metadata.
the json column should be parsed by a Zod schema when going in and out of the db.
that schema for now should only contain a single property, "drumCounts", which itself is a record from drum name in camelCase to the number of that drum type in the kit layout.
do not implement the parsing and validation of the drum layout file upon upload - just have a TODO there for me to implement.
use the same upload flow and logic as the maps upload endpoints. if possible, refactor it to be reusable to this as well.