Design Question on Integrating Effect with Drizzle for Backend Models
Bit of a design question. I get a sense that the effect/sql package (specifically the model parts) is designed to work together with effect/platform http api in separating interface from implementation, so that schemas can be used on the frontend as well with
HttpApiClient.make
HttpApiClient.make
. Is this the intent?
If so, are there any plans to make API to enrich Model classes on the backend so that they are annotated with drizzle-specific metadata and can be used to create drizzle table schemas? Its not clear how to cleanly integrate drizzle with the design style that Effect espouses, since drizzle doesn't quite do that