(I couldn't find community guidelines, hopefully this is not a violation) I am working on a prisma -> graphQL API generator and have an early version that would benefit from feedback. The gist: One adds doc-annotations to the prisma schema and gets an API server with: 1. GraphQL schema (CRUD & extensible) 2. Apollo resolvers (apollo-micro) 3. Seeder scripts for mock data. The product is implemented as a Prisma generator, so there are no additional abstractions, just • Prisma (+doc annotations) •  Apollo •  GraphQL I don't have public collateral - landing pages and the like - yet. Hoping for a show-and-tell in exchange for feedback. At your option, a trial is possible. If this looks interesting, please (PLEASE!!) reach out (sramam@gmail.com).

Hey @sramam 👋 this sounds really useful! Looking forward to see this project evolve 💯

Thanks @nikolasburk. The fundamental difference is that I do not use nexus. At least to my mind, it makes things a lot simpler - hopefully it'll resonate with others.

The fundamental difference is that I do not use nexus.

Yes, that’s what I understood from your previous message as well 😄 the approach you’re using is called SDL-first (also sometimes called schema-first) whereas libraries like Nexus, TypeGraphQL or Pothos are referred to as code-first 🙂 Pal.js is generating the CRUD operations for the SDL-first approach as well, so you should be able to use it 🙌

nitpick: s/Photos/Pothos/ 😄

Thanks, fixed 🙏 😄