The GraphQL Conversation Shouldn't Be the Same

The API for now is rest. We do have a dashboard and I s SDK playground, which feels at least to me feels a lot like those GraphQL clients that you have with schema there. And especially because we we code gen types for you based on your your databasescheme. So it feels like you have my GraphQL and stuff like that. It feels almost declarative to me. Yeah. Unless the API is your service, like you're not actually going to you don't really need the dynamic behavior of GraphQL. If you control the client and the server, in fact, you're just paying extra cost to actually parse through the GraphQL query and validate it or all