You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when you're publishToConnections, why do you have to execute the schema knowing the handler has been modified, why not just return the payload to the websocket as is like you commented here
// execution of subscription with payload as the root (can be modified within the resolve callback defined in schema)// will return the payload as is by defaultconstpayload=awaitexecute({schema: schema,document: parse(sub.subscription.query),rootValue: eventPayload,contextValue: graphqlContext,variableValues: sub.subscription.variables,operationName: sub.subscription.operationName,});// transform it into ws message (id is not specific to connection but to subscription)constmessage: NextMessage={id: sub.id,type: MessageType.Next,
payload,};
why not just send the payload as is without the execute, i think the execute is not effective.
Hi @hansottowirtz super awesome work!
I was trying to get subscriptions working with type-graph schema, but the
resolveSubscription
doesn't get the topic and filterCan i provide the example repo ?
The text was updated successfully, but these errors were encountered: