Add responseFromCache metadata to DataSourceFetchResult

[Rikusor]

Hello,

I tried to use the 6.4.0 version's responseFromCache metadata, in a customised solution where our approach is basically

  override async fetch<TResult>(path: string, request: DataSourceRequest = {}) {
    // Create messageId that will be used during the whole request lifecycle
    const messageId = this.getAzureMessageId();

    // Attach messageId to the request headers. Include other headers from client's request.
    request.headers = {
      ...request.headers,
      'x-message-id': messageId,
    };

    // Execute the request
    const result: DataSourceFetchResult<TResult> = await this.semaphore.withLock(() => super.fetch(path, request));

    // Only log request and response for no-depduplicated, successful requests
    if (!result.requestDeduplication.deduplicatedAgainstPreviousRequest) {
      this.logRequest(request as ApolloRequestOptions, path).finally();
      this.logResponse(request as ApolloRequestOptions, result).finally();
    }

    return result;
  }

In this implementation it would be required that I actually get this meta data part of DataSourceFetchResult -- So this can be sent to our logging platform correctly.

@smyrick Have I understood something wrong in this, and is there way for me to use your implementation here without these changes?

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[smyrick]

@Rikusor Yep, good catch. I didn't propagate the value all the way up. To validate I added more tests and implemented the same here: #381

You can either add those to your PR if you want or we can close and merge

[Rikusor]

Thanks @smyrick will close this PR.