Open mdugue opened 2 years ago
interestingly the behavior is different when quering arrays, here the results seem to get merged. Eg, sending those two queries
const POKEMONS_NAME_QUERY = gql`
query Pokemons {
pokemons(limit: 10) {
id
name
}
}
`;
const POKEMONS_MAXCP_QUERY = gql`
query Pokemons {
__typename
pokemons(limit: 10) {
id
maxCP
}
}
`;
leads to a merged preview:
I experience the same behaviour. We are using very few endpoints throughout the app with lots and lots of different queries on them. I thought the explorer view as a tool to see the merged state (since we are using graphcache).
Seeing this too, even when supplying a schema. Making multiple queries on an Enrolment
type, each requesting a different set of fields. Each query overwrites the previous one, and I would expect the fields to accumulate.
Hi,
First of all: 1. I'm not sure if this is ideed a bug but it looks pretty much like this to me. 2. I'm more than grateful for this great tooling and the work being done on it!
I just stumbled on a problem, which I think can be boiled down to this: When I send 2 queries to the same top-level schema-Query field with different selections – but same variables or none –, only one of them will be visible in the DevTools Explorer. For example, sending those 2 queries:
and
leads to either
name
ormaxCP
beeing shown in the Devtools Explorer (apparently the first response coming in)Why is this happening, shouldn't the results be either merged or shown as 2 different entries? Is this related to the devtools at all or rather to internal caching? (Btw: I couldn't see any difference between standard document cache and graphcache)
reproducible via https://codesandbox.io/s/urql-devtools-overriding-results-kqr91
Thanks a lot in advance!!