Feature request: GraphQL subscriptions

[gothy]

Thanks for your great work! 👍

It's be great to see subscriptions support in the future since they're supported all over the major GQL-as-a-service backends these days and it's the major selling point to use graphql (for me) :)

[jamesmacaulay]

I forgot to include it in the "future plans" section of the readme, but this is definitely something I'd like to support!

[xtian]

@jamesmacaulay Do you have any thoughts on how subscriptions should be implemented? I'm interested in working on this

[jamesmacaulay]

@xtian I haven't researched subscriptions very deeply so I don't have many strong opinions about it. I can think of a couple broad constraints though:

• The solution should be able to accommodate all the current major server implementations and ideally be forward-compatible with however the spec ends up.
• The primary interface for defining subscriptions shouldn't have any dependencies on the transport layer.

Contributions are welcome if you'd like to dig in! Please just share your work-in-progress as you go to keep the feedback loop tight.

[birge]

Is there any update on this? Would love to start using this in a project but subscriptions are a high priority. Great work so far though, thank you.

[xtian]

For our project we actually switched to using dillonkearns/graphqelm which has subscription support for our back-end (Absinthe).