docs VS nestjs-auth-graphql-starter

The syntax plugins for Prisma ORM auto-format their schema files in a similar way [1]. It bothers me so much that I can't bring myself to use their solution - which I realise is incredibly petty :)

[1] https://github.com/prisma/docs/blob/main/content/200-concept...

https://github.com/prisma/docs/issues/1652 It's almost as if when you're biased, you only find what you are looking for.

Ha, thanks a lot for catching this, just fixed it ✅

That's fair! I'm actually with you that proper documentation contributes a lot to a positive developer experience and while it seems like a detail, I totally understand how this feels off putting! I've created an issue for this forwarded it to our docs team to get this fixed very soon. Thanks again for reporting!

What exactly do you mean with a bulk API? As of now, Prisma provides updateMany and deleteMany operations. There's also the $transaction method which you can use for bulk creates and other bulk operations (plus we're also working on extending the Prisma Client API, e.g. with `createMany operations).

If you want Typescript maybe my NestJS starters for TypeORM and MikroORM are more up your alley. (;

As for project setup, something as big as Upwork in a production environment IMHO would be using a framework like NestJS instead of barebones ExpressJS, as it offers more abstractions. If you'd like to see how I implemented all the features an API like that would need, I urge you to check out my NestJS GraphQL w/ authentication boilerplate! It also features REST endpoints if you don't want to use GQL.

I've been using TypeORM for a good while now. I also have a boilerplate where I use it in NestJS, since that's my backend framework of choice, and am currently working on an analog version of that one using MikroORM.

I also have a boilerplate which I can always clone and get started with quickly. This makes it a very streamlined process as it also uses GraphQL-Utils to help me optimize queries with SQL.