You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm opening this issue to address the fact that the Apollo InMemoryCache instance created by render-runtime uses by default the HeuristicFragmentMatcher. Also it has no way (like an opt-in option) to use the IntrospectionFragmentMatcher.
This means that Queries or Mutations that use GraphQL Unions or Interfaces don't work correctly with the cache. For that reason, clients may have Query/Mutation issues without even knowing why data is incorrectly fetched (because the cache gets in the way).
IntrospectionFragmentMatcher poses the disadvantage of requiring schema-knowledge for correct execution (https://www.apollographql.com/docs/react/advanced/fragments/#fragments-on-unions-and-interfaces). An approach to make this feature available needs to be thoroughly thought of.
The text was updated successfully, but these errors were encountered:
I'm opening this issue to address the fact that the
Apollo InMemoryCache
instance created byrender-runtime
uses by default theHeuristicFragmentMatcher
. Also it has no way (like an opt-in option) to use theIntrospectionFragmentMatcher
.This means that Queries or Mutations that use GraphQL
Unions
orInterfaces
don't work correctly with the cache. For that reason, clients may haveQuery
/Mutation
issues without even knowing why data is incorrectly fetched (because the cache gets in the way).IntrospectionFragmentMatcher
poses the disadvantage of requiringschema
-knowledge for correct execution (https://www.apollographql.com/docs/react/advanced/fragments/#fragments-on-unions-and-interfaces
). An approach to make this feature available needs to be thoroughly thought of.The text was updated successfully, but these errors were encountered: