Correct network response but incorrect data object

[Kelbie]

There seems to be a problem with react-apollo-hooks in that the response is correct but when I print out the data object in useQuery its incorrect. Anyone any clues as to how to fix this?

[Kelbie]

I found the issue. Its because they all had the same id so react-apollo-hooks must assume its the same object when they are not. I think this should be fixed as its not something that happens using other graphql tools.

[ghost]

Maybe the best way is to create a unique identifier (uuid) based on depth of you results, index, and id from your backend and then config your inMemoryCache. Like this you can keep your id field for some operation and keep the mechanism of auto caching of your apollo client.

Or you can disable caching for this query.