Rafał Pitoń

@Sergei-Rudenkov this is not possible currently. Ariadne is using graphql-core v3 while Graphene is still on v2, and both of those versions share same namespace.

@Sergei-Rudenkov Sorry but no. I'm not able to put time now to dive into Graphene internals to develop thing like that.

I have an idea for changes to `make_executable_schema` that Ariadne GraphQL Modules implements that would make Graphene's v3 types work. There would be either a mixin or pass-through function that...

Next Ariadne GraphQL Modules is designed to support multiple approaches (APIs? frontends?) to type definition to solve this issue. But we would still need a Graphene-like API for types definitions...

This can be delayed after next API is released.

My only worry is that v1 module change will be a nasty surprise to everyone who just updates GraphQL Modules to new version and expects it to work.

Hello, thanks for opening a PR! If you are still want to contribute, please rebase on master to resolve the conflicts and and also add your changes to versioned documents...

My only real complaint lies in its design: its broken beyond repair with no clear pattern or scheme in it. First thing that I would do would be creating directories...

> The fact that this library requires pre-defining the queries that will be exposed through the Client class seems incredibly limiting. Is this a practical observation from a project you've...

API proposal: ```python result = await client.query( Query.user(id="123").fields( User.id, User.email, User.group.fields(UserGroup.id), User.reviews(category="123"), ), Query.user(id="fsadsa").alias("wohoo").fields( User.id, User.email, User.group.fields(UserGroup.id), User.reviews(category="123"), ), Query.search(query="test").on( "User", User.id, User.email, ).on( "Thread", Thread.id, Thread.title, ), operation_name="HelloWorld" )...