x-boilerplate VS TypeGraphQL

Heres a full ts with auth, cruds, etc : https://github.com/kaviarjs/x-boilerplate

I know it's not Sequelize, but this boilerplate with MongoDB can serve as an example on how we do things GraphQL, how to structure files, etc.

In terms of structure, how we do it, you can see aworking example here (very opinionated), but it can serve you as a way to wrap your mind around all these concepts.

You mean you want to see the source code? We do have such servers built with our framework. There you have guidelines on how to do things and here you've got a boilerplate. I cannot share the source code of a real production app with you unfortunately, but if you have specific questions (how to protect against nested deep attacks, etc) I can gladly answer you.

Start playing now with the boilerplate

Start hacking away with ready-to-use boilerplate: https://github.com/kaviarjs/x-boilerplate

In this tutorial, we're building a simple application which uses Cerbos inside of a GraphQL server. The server is written in typescript and uses type-graphql to create the schema and resolvers, and TypeDI to handle dependency injection.

Using decorators required setting an --experimentalDecorators experimental compiler flag. Several popular TypeScript libraries, such as type-graphql and inversify, rely on this implementation.

TypeGraphQL

Have you tried TypeGraphQL v2 (it's in beta). Some in this thread have reported success with it.

When moving away from Apollo Server, and you're looking for a replacement built with JavaScript or TypeScript, let me give you some options. If you want to keep building your GraphQL API schema first, you might want to consider Mercurius (which relies on Fastify) or GraphQL Yoga. If you're going to build your GraphQL API code or resolver first, have a look at TypeGraphQL or Nexus. Alternatively, there are great GraphQL-as-a-Service solutions such as StepZen in case you no longer want to build, maintain and host your own GraphQL API.

There are two main approaches to keeping the types of the GraphQL schema and entities in business logic in sync. You can generate the schema based on your TypeScript code (e.g. TypeGraphQL), or you can generate types based on your schema (e.g. GraphQL Code Generator). We opted for the latter since it slotted right into our existing GraphQL server implementation using Apollo Server.

I've used tools (e.g. TypeGraphQL) in the past, and for smaller schemas I've just manually written the schema.

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.