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

Support graphql-transport-ws websocket subprotocol #65

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

SmileyChris
Copy link
Contributor

Make some small changes to also support the graphql-transport-ws implemented and defined at https://github.com/enisdenjo/graphql-ws

@pranavdxl
Copy link

Any plan to merge this?

Copy link

@oliver-sanders oliver-sanders left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good. I rebased this onto upstream/master and tested with the JS graphql-ws client (which confusingly uses the graphql-transport-ws protocol), worked a charm 👍.

oliver-sanders added a commit to oliver-sanders/cylc-uiserver that referenced this pull request Aug 9, 2023
* The protocol for message exchange employed over a websocket
  connection is referred as the subprotocol.
* We currently use the `graphql-ws` subprotocol for serving GraphQL
  subscriptions over websockets.
* The JavaScript library which implements the `grahpql-ws` subprotocol
  is no longer maintained.
* This PR adds support for the `graphql-transport-ws` subprotocol,
  allowing us to migrate our client away from this unsupported library.
* This requires graphql-python/graphql-ws#65
  and a new release of the Python graphql-ws library to work.
@oliver-sanders
Copy link

@SmileyChris Do you have write access to this repo?

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

Successfully merging this pull request may close these issues.

3 participants