-
Notifications
You must be signed in to change notification settings - Fork 63
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
Incompatibility with GraphQL clients for subscriptions #123
Comments
Was this fixed by #124 ? |
Probably not. To fix this issue, the specified by: https://github.com/enisdenjo/graphql-ws/blob/master/PROTOCOL.md Currently, specified by: https://github.com/apollographql/subscriptions-transport-ws/blob/master/PROTOCOL.md (The naming of the library and protocol does not match, which is confusing) I suspect It is needed to change the implementation of |
So I think this was fixed by #126, right? |
Oh, right, #126 isn't merged yet. |
Most GraphQL client libraries have moved on from using the
subscriptions-transport-ws
(which is no longer maintained) implementation in favour ofgraphql-ws
for subscriptions.This causes compatibility issues, as in our case, we are trying to use the ApolloGraphQL client and lacinia-pedestal server and are unable to do so.
To enhance compatibility with client libraries, it would be great to move to the newer
graphql-ws
implementation.The text was updated successfully, but these errors were encountered: