Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

graphql-ws-next #90

Open
callumforrester opened this issue Nov 26, 2021 · 4 comments
Open

graphql-ws-next #90

callumforrester opened this issue Nov 26, 2021 · 4 comments

Comments

@callumforrester
Copy link

I have forked graphql-ws-next (fork) and made changes to make it compatible with graphql-core v3. Would there be any interest in integrating these chagnes into graphql-ws or are the two totally split now?

@SmileyChris
Copy link
Contributor

SmileyChris commented Nov 26, 2021 via email

@callumforrester
Copy link
Author

I'm not sure given how different graphql-ws and graphql-ws-next have become. Would the existing tests cover backwards-compatibility?

@callumforrester
Copy link
Author

Also there is currently

install_requires =
    graphql-core==2.*

Which might be difficult

@callumforrester
Copy link
Author

Another issue, adding a dependency on graphql-core>=3 conflicts with a lot of test dependencies (see below), so they would presumably have to be updated and tested.

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
graphql-relay 2.0.1 requires graphql-core<3,>=2.2, but you have graphql-core 3.1.6 which is incompatible.
graphene 2.1.9 requires graphql-core<3,>=2.1, but you have graphql-core 3.1.6 which is incompatible.
graphene-django 2.15.0 requires graphql-core<3,>=2.1.0, but you have graphql-core 3.1.6 which is incompatible.

Backwards-compatibility is not looking promising at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants