# All channels
Sachin D. Shinde@sachin-shinde
The updateQuery callback for fetchMore is deprecated
The updateQuery callback for fetchMore is deprecated, and will be removed in the next major version of Apollo Client. I removed updateQuery function from fetchmore and added typePolicy merge function, still warning exists. my types are:
How to troubleshoot "Invariant Violation" exception?
Hello, I just published a simple Typescript / Gatsby / Apollo Client application to prod, and I'm seeing a weird exception in my error reporting. The exception is: Invariant Violation: 44 (see https://github.com/apollographql/invariant-packages) …
How to use useQuery in SSR?
Hi guys, I have been trying to use Nextjs and Apollo client, however I can only make work queries inside getInitialProps on Pages in Nextjs, I'm trying to use getDataFromTree to let the queries be closest as possible the components, however I only get SSR of the queries inside…
Trying to connect to multiple endpoints.
Hi, I have an application built with NextJS and Apollo Client which work great. I deployed this application in Kubernetes and created a CICD(Jenkins Pipeline) that automatically build the Docker Image and then deploys it in 3 different environments. Development. …
How can you access "Watched Queries" from ApolloClient?
In the ApolloClient DevTools, the "Queries" tab will show you "Watched queries," which is handy indeed. Is there a way to similarly get at the currently "watched queries" from the ApolloClient API directly? The reason I'm asking is because I have a query that gives the user a…
How do I avoid prop drilling when using apolloClient for state management?
With something like the ContextAPI you have access to useContext so you can avoid prop drilling. How do I go about doing that with ApolloClient state management? I've found my self having to pass down data and functions to trigger events up and down my components.
Handling cache misses for local state in @apollo/client 3.0
I want to be able to handle cache misses from @client directive queries without having to manually include a code path cache misses for each local resolver function. From what I can tell, in the apollo-link-state days this would've been a lot more straightforward to handle at…
I just updated from 3.1.4 to 3.1.5 and it broke all parts of the code that use onCompleted callback for useQuery. Normally I can destructure the parameter right away but now I get this: TypeError: Cannot destructure property 'getTasks' of 'undefined' as it is…