Thanks for the tip. You might want to update your Apollo example. Looks like IntrospectionFragmentMatcher does not exist in Apollo 3.0, should be using PossibleTypes now.
I guess the problem we are trying to solve is trying to make our app’s UI more optimistic. Ideally we will be updating the cache first as an operation is taking place. So if we update a record, the changes show in the UI immediately. In the past we have handled this using Apollo’s cache and useMutation hook, which does it for us. We love the DatoCMS GraphQL API, but are trying to figure out a strategy using your Content Management API. We are using the Real-Time api to keep the DB and cache in sync, though that still ultimately requires a fetch, and are wondering what your preferred strategy for cache management is using the Content Management API while keeping the UI optimistic. Should we be manually updating the cache when using that API?