graphene-sqlalchemy VS Graphene

I have a project in python 2.7 and started migrating it to 3.9, after some upgrades I started getting this error "AttributeError: entity" similar to this issue. I already googled similar issues and I think it has to do with a relationship or table class model. Is there a way I can check if my table class models and relationships created properly.

Before we add the other objects to this file, let’s discuss what we have so far. We imported our models from our models.py file. Then we are creating our class UserObject, which we can see extends the SQLAlchemyObjectType – a class provided by graphene-sqlalchemy to integrate SQLAlchemy and GraphQL. The user_id attribute tells graphene to use the id associated with the model in the database, rather than the unique id graphql provides. You don’t need to use this attribute if you don’t want to, I find it useful for my applications. Finally, we are classing the inner class Meta that allows us to set different options. We are telling graphene_sqlalchemy to use the UserModel and to use the Relay Node.

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).