useResponseCache: How to invalidate cache with apollo federation

[kanopa]

I have two services that communicate with each other through a gateway using apollo federation, search and main backend with data
example query search where name resolve through federation

query Search($first: Int, $query: String) {
  search(query: $query) {
    example(first: $first) {
      nodes {
        id
        name
      }
    }
  }
}

When making a request, a request for one service saves only id and _typename, and the second service saves all other requested fields without id and _typename

After mutation only one of records is invalidating (record with id and _typename)
I did a little research on this, data with _typename and id on federation requests exists in onExecuteParams.args.variableValues
representations: [{ __typename: 'Post', id: '2838935f-751d-4497-b48a-5c747a6c75e9' }]

How to properly invalidate cache using apollo federation?

[kanopa]

I guess we need sth like this and call it on onExecuteDone

const processFederationResult = (processedResult) => {
                // if _entities exists in data it is federation response
                if ('_entities' in processedResult?.data) {
                    // need to add all representations to identifier for invalidation federation responses
                    onExecuteParams.args.variableValues.representations?.forEach(({ __typename: typename, id }) => {
                        identifier.set(`${typename}:${id}`, { typename, id });
                    })
                }
            }

[kanopa]

@kanopa do you think you can create a pull request on this repo that adds such an example to the examples folder? I think this will be a valuable resource for everyone using federation!

I had to do it using yarn patch and edited useResponseCache straight, maybe we can integrated this with useResponseCache?

[n1ru4l]

@kanopa Would this help you solve this issue in userland? #1517

[n1ru4l]

Hey @kanopa, did you have time to look into this PR?

[n1ru4l]

Hey @kanopa, any update?

[n1ru4l]

@kanopa I will close the PR and mark this discussion as solved, as there seems no need for this feature anymore.