@syrusakbary
Do we have any plan to support google app engine ndb in near future?
If not, I am willing to help.
Could you please guide me to which part I should start to do it?
Thanks
Hi @kiennt - As it turns out, graphene, graphql-core and graphql-epoxy in general doesn't have a preference for what kind of database backend you use. Although graphene does come with built in support for the introspection of Django models to generate a Schema, you could easily just manually define your Schema & Types to fit your NDB entity schema, and resolvers to query your database accordingly.
Hi @kiennt,
Yep, adding support for automatic Google App Engine NDB mapping to graphene would be great.
You can get inspired how graphene is doing with Django models mapping.
Everything should be similar except of the converter (which have to be adapted for converting the fields from NDB), and types.py which also have to be adapted for getting the fields from the NDB model.
+1
:+1:
Hey @kiennt, @cyrfer would love your feedback on https://github.com/ekampf/graphene-gae
Closing this issue, as @ekampf did a terrific job with graphene-gae, which is now part of the GraphQL-Python community.
[Would be great to have a PR into this repo adding the docs]
docs PR in the works...
Most helpful comment
Closing this issue, as @ekampf did a terrific job with graphene-gae, which is now part of the GraphQL-Python community.
[Would be great to have a PR into this repo adding the docs]