Ability to use graphql-ws instead of subscription-transport-ws

graphql / graphql-playground

🎮 GraphQL IDE for better development workflows (GraphQL Subscriptions, interactive docs & collaboration)

MIT License

8.75k stars 731 forks source link

Ability to use graphql-ws instead of subscription-transport-ws #1291

Open Amareis opened 3 years ago

Amareis commented 3 years ago

This issue pertains to the following package(s):

[ ] GraphQL Playground - Electron App
[ ] GraphQL Playground HTML
[X] GraphQL Playground
[ ] GraphQL Playground Express Middleware
[ ] GraphQL Playground Hapi Middleware
[ ] GraphQL Playground Koa Middleware
[ ] GraphQL Playground Lambda Middleware

subscription-transport-ws is (sort of) deprecated now: https://github.com/apollographql/subscriptions-transport-ws#graphql-ws I think it's not really hard to implement grapqhl-ws support.

Sytten commented 3 years ago

The community has moved to graphql-ws now, I think it would better for playground to move too.

brettjashford commented 3 years ago

there's a PR to add this in graphql-playground-react https://github.com/graphql/graphql-playground/pull/1295

maxpain commented 3 years ago

Any updates?

faboulaws commented 3 years ago

Ideally, the subscription client API should be a pluggable API. The subscription-transport-ws can be the default Handler (or Interface implementation) for backward compatibility. graphql-ws or other implementation/transport (such as SSE) can be used if wanted.

jspizziri commented 2 years ago

@acao , any updates on this?

elashpear commented 2 years ago

For those looking for an alternative client that does support graphql-ws until this issue is resolved, I recommend another FLOSS client called Altair: https://altair.sirmuel.design/