The current API is scuffed and unnecessary. GraphQL is slightly more fun and a lot better for client-side type info. The only downside with GraphQL is code duplication because prisma doesn't use classes for defining tables, but if we're ditching prisma that doesn't matter.
sylv
commented
2 years ago
The current API is scuffed and unnecessary. GraphQL is slightly more fun and a lot better for client-side type info. The only downside with GraphQL is code duplication because prisma doesn't use classes for defining tables, but if we're ditching prisma that doesn't matter.
Should probably do it after #16