Arie Bovenberg

Hi @x0y-gt thanks for creating this issue. Variables and mutations are not yet supported. Also not yet in the upcoming release. It is on the backlog of course, but will...

This seems like a very sensible feature. This overlaps with my thoughts on providing custom serialization for existing types. I've created an issue for this: #22.

hi @g-k, what do you mean exactly by serializing a `Query` to `JSON`? Perhaps a simple example can help. If a query looks like this: ```python query = schema.query[ _...

Hmm, I guess it makes sense for the raw JSON to be accessible in a query. I'll see if I can fit it into a coming release. As a current...

> This pattern looks a bit confusing, maybe I am not quite understanding it. How do these quiz.Serializer objects get related to the classes they are defined for? The `Serializer`...

Hmmm, what I think you're aiming for is to override the _base_ of all `Enum` classes. This will have to be a different mechanism from overriding specific classes. # Enum...

@rmarren1 great! I'd like to separate this from the serialization question for now, because I'll need to refactor some serialization stuff myself. I've created a separate issue for the enum...

Hi @stickystyle, thanks for creating this issue. There are currently no plans for implementing this, but it definitely makes to do so. Currently the `Schema` is tied to the JSON...

Note that it is possible to work around this issue by loading the schema from the GraphQL API itself (`Schema.from_url()`), which can be persisted to disk as JSON (`Schema.to_path()`, `Schema.from_path()`)...

@sobolevn my understanding is that it doesn't matter that `Base` doesn't have `__match_args__` or `__init__`, this should only matter for the `case` statements. ...but in the end the problem doesn't...