Usability and Self-contained-ness of DSL module in v2.x

[Datoclement]

(Not sure this is a place to ask these kinds of questions)

My current project with Graphene needs graphql-core==2.3.2 and therefore I can only use v2.x of gql library. I would like to use the dynamic query construction in dsl module. I am not sure whether this part of functionality is self-contained in v2.x. I tried to find doc for v2.x but cannot find it. And unlike other functionality, there is neither demo code on dsl in v2.x.

My question is: Is dsl a completed feature in v2.x?

Edit: I am currently looking at the v3 doc to try to understand dsl in v2 (I suppose they would be similar?) but I want to be sure that the code is at least tested and avoid unexpected behaviors.

[leszekhanusz]

V2.x is not maintained anymore.

At some point, there was a small example in the README.md

There was a lot of modifications in the DSL code since then:

• we now provide a schema instead of a client in DSLSchema and now we use the dsl_gql function with the DSLQuery, DSLMutation and DSLSubscription classes (Refactor DSL code #169). With v2.x you call the query and mutate methods of DSLSchema directly
• fragments are supported (DSL implementation of fragments #235)
• we can serialize complex arguments in inputs (DSL serialize complex arguments to literals #255)
• we can add variables (Add support for variable definitions in dsl #210)

There were also a few bugs fixed:

• Fixed the bug where a nested GraphQLInputObjectType causing infinite get_arg_serializer recursive calls #132
• DSL: Allow to use GraphQL keys named type #151

If you don't need those features and don't have recursive input objects, then it should work correctly.