Awesome, so basically layering GraphQL atop channels rather than having them coexist side-by-side.
This is very interesting and addresses one of my earlier questions: Replacing HTTP with Websockets (or other persistent transport). Why did you choose to transport queries via websockets rather than http? Are there any docs/articles written on this, specifically on the Absinthe side?
What I meant by “maintaining both” was having a scope for GraphQL and another for channels. I.e. you have, say, an Airbnb app whose browse/booking logic is routed to contexts by GraphQL resolvers but whose chat (or realtime bidding or wtv) is routed by channels. Is this an antipattern?
