Monorepo and schemas, how to structure
I was wondering if anyone had any advice/thoughts on how best to structure a monorepo project when it comes to schemas. I currently have a single "database" package that has all my schemas and migrations.
Is there a "better" way to do it?
It seems wrong to have the schemas separate form the package that it relates to, but at the same time it seems simpler than trying to figure out a way to manage schemas and migrations across multiple packages..
0 Replies