apollo | Java libraries for writing composable microservices | Microservice library

It appears that the option you'll want to use to target the WS connect/disconnect event is connectionCallback (see full list of WebSocketLink options here).

Take a look at lines 620-635 of the WebSocketLink source and you can see that the provided connectionCallback is called both for GQL_CONNECTION_ERROR and GQL_CONNECTION_ACK received message types. Therefore, you should be able to target both events using this callback.

I haven't used Apollo's WebSocketLink yet myself, so I am unable to confirm that this will work fully as expected. Additionally, the behavior to fetch all missing chat messages upon reconnect is something you may need to build yourself as it doesn't appear to be part of the default reconnect behavior (will depend on server implementation; see Apollo Server docs). Conversely, it does appear that WebSocketLink will forward all unsent messages to the server upon reconnect by default.

bug with React Native 0.62+ that messes up the configuration for multiform requests. It can be fixed by commenting out line 43 in android/app/src/debug/java/com/maxyride/app/drivers/ReactNativeFlipper.java:

There's an issue with vuetify I think. But if you use yarn, you can use

I wasn't quite able to follow what you're really asking, do you just want to find seo by id, and it might be in the results, which might be an array of null values, or null itself?

In that case const seo = seoDataObject?.filter(x => x.node).find(x => x.node.id === id)?.node.seo;

I think you have not fully understood Next.js yet. Next.js renders views on the server or alternatively sends "server side props" to the client. This means getServerSideProps gets executed on the server (as the name suggests). Cookies are a feature of the browser. So what happens?

1. Browser sends request to Next.js. If your Next.js server and your GraphQL server are on the same domain, the request includes the Cookie header.
2. Next.js receives request and executes getServeSideProps.
3. Next.js Apollo Client makes request to server, missing the cookies, because the cookies are only in the browser's initial request!

This means you would have to first make sure that your Next.js server receives the cookies from the frontend. This should happen automatically, if it is on the same origin as the GraphQL server. Otherwise it is a bit tricky and it should be easier to work with an explicit Authorization header in this case. Then you have to pass on the cookies with the request. This can be done by accessing req in getServerSiteProps and using the context in client.query.

With SvelteKit the subject of CSR vs. SSR and where data fetching should happen is a bit deeper than with other somewhat "similar" solutions. The bellow guide should help you connect some of the dots, but a couple of things need to be stated first.

To define a server side route create a file with the .js extension anywhere in the src/routes directory tree. This .js file can have all the import statements required without the JS bundles that they reference being sent to the web browser.

The @apollo/client is quite huge as it contains the react dependency. Instead, you might wanna consider importing just the @apollo/client/core even if you're setting up the Apollo Client to be used only on the server side, as the demo bellow shows. The @apollo/client is not an ESM package. Notice how it's imported bellow in order for the project to build with the node adapter successfully.

Try going though the following steps.

1. Create a new SvelteKit app and choose the 'SvelteKit demo app' in the first step of the SvelteKit setup wizard. Answer the "Use TypeScript?" question with N as well as all of the questions afterwards.

'optimisticResponse' is the option for this case.

It's often possible to predict the most likely result of a mutation before your GraphQL server returns it. Apollo Client can use this "most likely result" to update your UI optimistically, making your app feel more responsive to the user. https://www.apollographql.com/docs/react/performance/optimistic-ui/

Using readFragment covers my expectation. previously I have tried this solution but wrongly, ex:

It's strange but the problem was with this import { GraphQLDateTime } from 'graphql-iso-date'; package.

After removing it from the schema, it started working.