Support new graphql-ws subprotocol

[Quantumplation]

At some point, the graphql community made the breaking change to switch to a new websocket subprotocol; What was previously called the graphql-ws subprotocol is now called graphql-transport-ws. N.B. Confusingly, the standard library implementing this in the js world is called graphql-ws, making this non-trivial to track down, as I kept thinking that graphql-ws was the more modern one.

It would be super helpful to support the new spec.

See:
https://www.apollographql.com/docs/apollo-server/data/subscriptions/#switching-from-subscriptions-transport-ws
https://github.com/enisdenjo/graphql-ws/tree/master/docs
https://github.com/enisdenjo/graphql-ws/blob/d44c6f18ccd2bc539bb541e6bfd1bf0c769c7856/src/common.ts#L10-L15

[pavelnikolov]

@Quantumplation this would indeed be very helpful. PRs are more than welcome.

[Quantumplation]

@pavelnikolov Super swamped with work right now, but I might have some spare time in a week or two!

[andig]

Cross-ref hasura/go-graphql-client#38. As of now I'm totally lost with old vs new. Seems the Go landscape has server, but is missing client support for the "new" graphql-ws from what I understand?

[mikhailv]

I have adapted implementation of graphql from gqlgen for graph-gophers. Just finished and tested just a little, but it works for me. Will do some additional testing tomorrow.

https://github.com/mikhailv/graphql-transport-ws

[andig]

https://github.com/hasura/go-graphql-client meanwhile has support, too.

[mikhailv]

https://github.com/hasura/go-graphql-client meanwhile has support, too.

@andig but this this client only library, right? Not server websocket handler for gophers graphql?

[annibuliful]

Any progress for this issue
I'm a newbie in golang

[pavelnikolov]

Note that I am aware of.