-
Notifications
You must be signed in to change notification settings - Fork 89
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
Comments
If we can integrate it then that'd be great! Best case would be we can keep
backwards compatibility -- do you think that's possible?
…On Fri, 26 Nov 2021 at 23:54, Callum Forrester ***@***.***> wrote:
I have forked graphql-ws-next (fork
<https://github.com/callumforrester/graphql-ws-next>) 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?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#90>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA227YRMKQ7J3PXDFQKYX3UN5RNTANCNFSM5I2MFEPA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I'm not sure given how different graphql-ws and graphql-ws-next have become. Would the existing tests cover backwards-compatibility? |
Also there is currently
Which might be difficult |
Another issue, adding a dependency on
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
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?
The text was updated successfully, but these errors were encountered: