Tag: graphql-ws
-
onConnvect, graphql-ws subscription
0 thank you for your time, my problem is that i want to return the data to the client immediately after subscribing. I know about the onConnect method, but it is called before JwtAuthGuard. What is the best way to do this? I was thinking of moving the authorization logic to onConnect. To better understand…
-
in my localhost subscription is running but on server it is not wroking , throwing above message
-1 { "message": "Failed to construct ‘WebSocket’: An insecure WebSocket connection may not be initiated from a page loaded over HTTPS." } in my localhost subscription is running but on server it is not wroking , throwing above message. i want to run on server … graphql subscription wss ws graphql-ws Share Follow asked 10…
-
Graphql-WS subscription always returning the whole data set instead of the the delta
0 I am using the graphql-ws library for subscribing to the following data: export const x = gql` subscription x($user_id: uuid!, $contact: uuid!){ chats(where: { user_id: { _eq: $user_id }, contact: { _eq: $contact }}) { title }` I subscribed as follows: const subscription = client.subscribe({ query: x, variables: { user_id: …, contact: … }…
-
Cannot read properties of undefined (reading ‘FIELD’) when bumping @apollo/client to 3.8.x
0 I have a particular feature where I require to implement a second graphql client (using @apollo/client) that uses the old ws protocol for subscriptions – the other graphql client uses the latest one. This is a code snippet of a codesandbox link import React, { useState } from "react"; import reactLogo from "./assets/react.svg"; import…
