document how to use persisted queries about graphql-ws HOT 5 CLOSED

Good idea! We should offer a handler like that.

However, onOperation is a better suited name for when an operation resolves, and onSubscribe for immediately when the user requests a subscription (operation execution).

The current onSubscribe has to change. Even if its a breaking change, its worthwhile! Check #40 out.

from graphql-ws.

Currently you'd have a hard time setting up persisted queries because AST parsing is run on the subscribe payload query before the onSubscribe.

https://github.com/enisdenjo/graphql-transport-ws/blob/e9d8ee45487f2a81c493b1b6d8d1c209111ff878/src/server.ts#L403-L436

I will lift this limitation and then you should be able to request something like this:

{
  "id": "unique-transport-id",
  "type": "subscribe",
  "payload": {
    "query": "persisted-query-id",
    "variables": { "hey": "there" }
  }
}

Find the persisted query in onSubscribe, supplement it, validate and then execute.

from graphql-ws.

Could we implement a handler that is run before that e.g. onOperation?

from graphql-ws.

🎉 This issue has been resolved in version 1.9.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from graphql-ws.

Quick heads up, @n1ru4l, [email protected] just landed, adding the extensions field in the subscribe message payload.

This means that you now can pass along the persistedQuery through that field on each subscribe as various other libraries/frameworks suggest. And of course, extend with your custom requirements. 😄

from graphql-ws.