graphql-go
graphql-go copied to clipboard
Any plans to support enisdenjo/graphql-ws?
The current subscription example implements Apollo's [email protected] protocol but this protocol is no longer being maintained:
From the README in apollographql/subscriptions-transport-ws:
The subscriptions-transport-ws library is not actively maintained. It is recommended that you use the graphql-ws library instead.
Are there any plans to add support for the enisdenjo/graphql-ws subscription protocol?
Hi @gerarts
This was just a reference implementation and it is not production ready. The graph-gophers/graphql-go library is protocol agnostic as it works with Golang channels.
With that being said, we would be moving towards graphql-ws support but it is not an immediate priority. PRs are more than welcome.
With graphql-ws, I could not connect to go graphql server (different protocol?) With subscriptions-transport-ws, I could not use vite, since subscriptions-transport-ws does not support ESM build. There is some rollup config to use subscriptions-transport-ws in client build, but if I use vite SSR, it is not effective.
I'm closing this issue as the library is agnostic to protocols. It returns a Golang channel and you can use it with any protocol you want. We might add a reference implementation of the graphql-ws protocol in future but it is now in our immediate roadmap. PRs with a working example would be more than welcome.