Hey Francisco great article, easy to read and concise.
I'd add to the cons of the schema first approach the schema/data duplication while using an orm.
For example with prisma you'd have your .schema file from prisma and your graphql schema in other
But I think Prisma and TypeORM would be an exception if you used TypeGraphql, in Prisma's case the graphql schema would be generated according to Prisma's schema. Whereas with TypeORM you would use entities as a base without needing to define your schema.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Francisco great article, easy to read and concise.
I'd add to the cons of the schema first approach the schema/data duplication while using an orm.
For example with prisma you'd have your .schema file from prisma and your graphql schema in other
Thanks! Yes you are absolutely right! ✌️
But I think Prisma and TypeORM would be an exception if you used TypeGraphql, in Prisma's case the graphql schema would be generated according to Prisma's schema. Whereas with TypeORM you would use entities as a base without needing to define your schema.