I’m refreshing the token this way (updated OP’s): import { ApolloClient } from ‘apollo-client’; import { onError } from ‘apollo-link-error’; import { ApolloLink, Observable } from ‘apollo-link’; // add Observable // Define Http link const httpLink = new createHttpLink({ uri: ‘/my-graphql-endpoint’, credentials: ‘include’ }); // Add on error handler for apollo link return new ApolloClient({ … Read more
query is something you just query for once, you can consider it as an equivalent of GET. watchQuery is something you constantly keep a watch on query, whenever that query will be refetched or the data related to that query is changed from anywhere else, this method will keep on emitting the updated data. It’s … Read more
The props added by your firstQuery component will be available to the component below (inside) it, so you can do something like: export default compose( graphql(firstQuery, { name: ‘firstQuery’ }), graphql(secondQuery, { name: ‘secondQuery’, skip: ({ firstQuery }) => !firstQuery.data, options: ({firstQuery}) => ({ variables: { var1: firstQuery.data.someQuery.someValue } }) }) )(withRouter(TestPage)) Notice that we … Read more
The example given in the the Apollo Error Link documentation is a good starting point but assumes that the getNewToken() operation is synchronous. In your case, you have to hit your GraphQL endpoint to retrieve a new access token. This is an asynchronous operation and you have to use the fromPromise utility function from the … Read more
To workaround the CORS issue with Apollo you have to pass the no-cors option to the underlying fetch. import ApolloClient from “apollo-boost”; const client = new ApolloClient({ uri: “your client uri goes here”, fetchOptions: { mode: ‘no-cors’, }, }); This is not a specific Apollo problem, rather a configuration that is meant to be tackled … Read more
Two Solutions There are two ways to do that. One is quick and easy and will work for a specific query with some limitation, and the other is a general solution that is safer and can work for multiple queries. Quick and Easy Solution Advantages it’s quick and… easy When you configure your query you … Read more
You should use the mutate method of the client for mutations, not the query method. The options for the method can be found in the docs. Apollo is opinionated about how queries and mutations are treated, so each method has different options that are appropriate to each operation’s behavior (for example, mutate includes a refetchQueries … Read more
Cleaning Unwanted Fields From GraphQL Responses In the above thread, I have posted the answer for this problem please refer to it
If you still want to use Apollo Boost in Node.js but need to polyfill the native fetch API of the browser, try out cross-fetch. I used it for my minimal example over here. And that’s how it can be used after installing it: import ‘cross-fetch/polyfill’; import ApolloClient from ‘apollo-boost’; const client = new ApolloClient({ uri: … Read more
You’re comparing apples to oranges. Yes, at a high level both redux and apollo-client provide a way for you to manage global application state. However, redux allows you to create a predictable state container that changes in response to the actions you define. That means redux offers: Predictability. Reducers are pure functions — given the … Read more