Christoph Zwerschke

GraphQL-core is a port of GraphQL.js. As soon as @defer is part of the standard and included in GraphQL.js, it will be ported to GraphQL-core as well. We don't want...

@flzozaya This will be eventually included in GraphQL-Core 3, but not in GraphQL-Core 2 (the legacy branch).

@arjunlol This is still only in an experimental branch in GraphQL.js, so it's not yet in GraphQL-core 3. We are also working on another mechanism to defer execution, see [PR...

@sebastiandev @sliverc Keep in mind that the idea of this project is to copy the functionality from graphql-relay-js over to Python. I think it is wise to stick to that...

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...

I suggest to get the ball ralling, we call the Py3-only version 3, and use this version numbers also for the other projects - i.e. Graphene 3 should be Py3-only...

> Which brings up a question. Does graph-core-next go away at that point? Are Issues, if relevant, preserved in some way? Commit history? Does anyone care about those things? Etcetera....

@eMerzh Still waiting to get the PyPI maintainer right for graphql-core in order to do that - will address this problem at our next meeting end of next week.

I think the problem should be solved fundamentally. First, I'm adamant that the maintainers of graphql-core need maintenance rights on PyPI and have the freedom to deploy to PyPI in...

This question still needs to be decided. We have two options: 1. Rename graphql-core to graphql-core-legacy and graphql-core-next to graphql-core. 2. Merge the graphql-core-next master into graphql-core, after creating a...