Comments (1)
Looking at ApolloClient's code, it looks like it merges client options with default options like this:
if (this.defaultOptions.watchQuery) {
options = {
...this.defaultOptions.watchQuery,
...options,
} as WatchQueryOptions<TVariables>;
}
Because React Apollo Hooks passes an options object with a fetchPolicy
key, it overrides the defaults (even if fetchPolicy
is null or undefined). I think the only way for this to work (without Apollo Client changing how it merges default options) would be to completely omit any unused options (in my case it's affecting fetchPolicy
, but it is probably also affecting errorPolicy
, etc.
React Apollo's <Query />
component deals with this by "compacting" the options before passing them on. See https://github.com/apollographql/react-apollo/blob/master/src/Query.tsx#L36 and https://github.com/apollographql/react-apollo/blob/master/src/Query.tsx#L277
There's also an open issue on apollo-client about this.
from react-apollo-hooks.
Related Issues (20)
- Unable to Access Result Attributes
- Calling a mutation within React.useEffect causes infinite loop HOT 9
- Error on refetch
- Apollo client not handing Throw Error networkError eg.400,500
- data is no longer defined in 0.5.0 before data is loaded HOT 2
- Archive repo
- TypeError: Object(...) is not a function
- Question: How can I abort a query already in progress? HOT 1
- useLazyQuery ignores request if one is in progress (or how to cancel running requests)
- Support for `renderToStream`
- Correct network response but incorrect data object HOT 2
- Prevent infinite loop with useQuery
- Does useQuery hook uses local state for storing the data it receives from the server ?
- useSubscription - Duplicated subscription on page refresh HOT 1
- Refetching useQuery with skip: true results in a network request but does not update data
- Testing useSubscription and no responses when other mutations being mocked
- dynamic input variables in react-apollo-hooks
- Is it possible to map the result of one query to another query? HOT 1
- Is there any way to use multiple queries before a component render inside the component itself?
- UseQuery is not calling any API in the network side, when I console.log response, I am seeing this. what could be wrong here?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from react-apollo-hooks.