Christoph Zwerschke

Note that this is the repository for the legacy v2 branch. Active development is happening in the v3 branch only (graphql-core-next repository). Adding new features here is difficult since this...

@Syrus 😃 Good to know. In fact as you see we could need a little help with maintaining v2. Also, since I'm having you on the phone: Do you think...

Btw, regarding compatibility between v2 and v3, can you have a look at graphql-python/graphql-core-next#77 which is a bit related?

To solve this, one would need to dig deep into the subscription code and add tests for subscribing to multiple fields (or improve the existing `test_accepts_multiple_subscription_fields_defined_in_schema`). Not sure if it's...

@sciyoshi Just to clarify: Do you think this is a bug in the reference implementation [graphql-relay-js](https://github.com/graphql/graphql-relay-js) or a bug in how graphql-relay-py implements it? It looks like the former since...

We can consider this after releasing 3.0 in the next version 3.1. It would be best if this would changed upstream in the JS version, so I will try that...

I'm currently trying to bring relay-py in line with the current versions of core and relay-js, and then reconsider the pending PRs and issues. Unfortunately, currently we cannot deploy new...

The problem with adding new features is that graphql-relay-py is a port of graphql-relay-js and we want to keep it compatible and up to date with the code and API...

Can you post a complete test case? Here is what I did trying to reprpduce it, but it works for me: ``` from graphql import * from collections import OrderedDict...

The current development is going on in [GraphQL-core 3](https://github.com/graphql-python/graphql-core-next). GraphQL-core 2 is not really maintained any more, and no new features will be added. Unless somebody volunteeers as maintainer of...