nestjs-custom-injector VS TypeGraphQL

https://github.com/EndyKaufman/nestjs-custom-injector - Source code of library https://nestjs-custom-injector.site15.ru/api - Demo application with nestjs-custom-injector. https://github.com/EndyKaufman/nestjs-custom-injector-example - Example generated with nest cli.

https://nestjs-custom-injector.site15.ru/api/#/abstract-class - Demo application with nestjs-custom-injector. https://github.com/EndyKaufman/nestjs-custom-injector/tree/develop/apps/demo/src/app/abstract-class - Example.

I'll be honest and say I don't think python is the right language to implement graphql. It's possible of course and if you're looking for a graphene tutorial, I'm sure you can find one (and I'll help you evaluate one, if you'd like). I'd personally go with node.js, typescript, and typegraphql.

Foal's dependencies have been updated so as to support the latest version of TypeGraphQL.

Essentially GraphQL is a method of querying and validating API endpoints. Generally you need to set up your own way to access your database in what's known as a resolver. An example of this can be found in the NestJS docs. Here you'll see both a code-first approach to creating a schema (specific to NestJS, but also applicable to TypeGraphQL) as well as the schema-first approach.

Some alternatives to Pothos are https://nexusjs.org/ https://typegraphql.com/

As of right now, I've arrived at the following: I'll use type-graphql in the server package to define the schema and resolvers using types and decorators (type-graphql is really attractive to me because of the dependency injection). type-graphql can then easily pass the schema to express + apollo server, and everything is automatically typed in vscode

In this post, I’ll help you get a solid understanding of working with GraphQL in Node.js and TypeScript using a library called TypeGraphQL. TypeGraphQL is an awesome way to create your GraphQL resolvers and it has seamless integration capabilities with ORMs like TypeORM (we’ll be using it in this post!) and mikro-orm. It uses classes and decorators to beautifully generate our schemas using very less code.

Instead of constructing an object, it uses classes to define the types and operations for the schema that it generates. The schema generated by this implementation will have the same structure as the schema created with graphql-js. Using classes to define your schema has the advantage of being less mutable and more structured when writing code. Similar implementations can be found for TypeScript with the library TypeGraphQL or Sangria GraphQL for Scala.

I use NestJS and just create classes with decorators, just like in their docs. No Prisma needed. The NestJS decorators are pretty much just a wrapper around the TypeGraphQL library (which you don't need NestJS for).

In my last project we were using code first with https://typegraphql.com/ and it was quite good.

Same. I paired that with https://typegraphql.com/ (which builds the graphql schema dynamically from the code using buildSchemaSync) and MikroORM (which you can overlap your entities with to remove duplication there) and it was a totally generated solution with full type safety.

A bit crazy complex to setup so many moving pieces, but once it is, it works great.