TypeGraphQL VS Graphene

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.

And gqlgen is not alone in this. We found several more GraphQL frameworks that don’t take it upon themselves to address this problem. Widely used GraphQL server implementations, such as graphql-go/graphql and Python’s graphene, have the exact same gap of exposing messages of unexpected errors by default.

There are multiple Python-based GraphQL libraries and they all vary slightly from each other. For the longest time, Graphene was a natural choice as it was the oldest and was used in production at different companies, but now other newer libraries have also started gaining some traction.

> But you need to know that Wasmer and its sibling projects will stay free forever. We are open source lovers, all of us, and we have a strong background on working on open source projects before joining Wasmer too.

That's great. I'm sure the closed source paid 10x faster editions of the graphene Python GraphQL server written by Syrus "CEO of Graphene" and CEO of wasmer will be open sourced in this spirit.

https://github.com/graphql-python/graphene/issues/268#issuec...

http://graphql-quiver.com/

CloudinaryField is a custom model field not a django built in one and graphene-python doesn't know what do with it. See the list of types it does https://github.com/graphql-python/graphene/tree/master/graphene/types

Thanks for the reply, I was looking at Strawberry a bit but not enough documentation for a graphql noob like me... Hate to turn this into tech support but could you potentially answer a question for me? I'm having a really hard time figuring out how to do this. Given this example: https://github.com/graphql-python/graphene/blob/master/examples/simple_example.py and a slight modification:

Graphene was one of the first (if not the first) lib built on top of graphql-core to provide an easy to use api to build graphql applications. It's been around since 2015 and has a lot of integrations built for it (e.g. Django, SQL Alchemy, etc).