Package: grafq
grafqgrafqis a library designed to help constructing GraphQL queries with idiomatic Python. It provides a concise and simple API to build such queries incrementally, with strong emphasis on correctness and type safety. Partial queries can be shared, composed and modified trivially, and fully formed queries can be converted to strings and reused infinitely with zero cost.ExamplefromgrafqimportField,Var,Queryfromgrafq.clientimportClientclient=Client("https://api.github.com/graphql",token=TOKEN)simple=Query().select("viewer.login","viewer.name").build()data=client.get(simple)schema=client.schema(strict=True)using_schema=(client.new_query().select(schema.repository(owner="asmello",name="grafq").url).build_and_run())composition=(client.new_query().var("size","Int").select(Field("viewer").select("login","name",Field("avatarUrl",size=Var("size"))),schema.repository(owner="asmello",name="grafq").url,).build_and_run(variables={"size":200}))FAQCan't I just type out the query directly?Yes, but usage of string literals with embedded code have a number of practical disadvantages:Poor IDE support- most IDEs aren't smart enough to detect that your string contains some GraphQL code and won't interpret the embedded code specially. This means loss of important productivity features like syntax highlighting, type hinting, reference validation and autocomplete. This can be sometimes worked around by placing queries in separate files, but that creates a number of overheads and error conditions that are best avoided.Error proneness- given lack of tooling support, it's much easier to make mistakes that won't be flagged until the code is executed in an integration test or in production.Poor integration- when represented as a string, embedded code has to be manipulated as such. This creates surface area for bugs and vulnerabilities, and makes dynamic queries just a royal pain to implement.Poor reusability- it's far too easy to end up just creating static ad-hoc queries everywhere, when often times there are reusable components that could be shared around. Fragments help avoiding that, but are hard to use correctly in practice due to (3).All of these (and other reasons) have led to the development of this library, which makes it possible to construct and manipulate GraphQL queries in a first class manner, using plain old Python objects.Did you mention type safety?Type safety is opt-in. If you use the Field API, you can create typeless queries that work just as well as typed ones. Then you delegate error-catching to the server, which may or may not provide useful context.If you choose to use the sugar-sweet TypedField API (accesible from a Schema object), however, every field and variable is validated as early as possible, client-side, as you build the query. Validation will still occur at runtime, but before the query is fully built and executes. Bear in mind that currently this has a noticeable overhead, as introspection queries are relatively expensive (but in the future better caching will minimise this).Further, there are plans to support generating schema classes staticallly, which can then be used for offline type-checking using Python's native type hinting system. This has the downside that the generated classes need to be kept in sync with the remote API, but it has the upside that IDE features (like type checking and auto-complete) can be leveraged to their full potential at virtually no runtime cost.