QueryRef data result type is wrong when using initial loading

[maxhov]

Describe the bug

When enabling initial loading, the type of valueChanges on QueryRef is not correct. The type is as follows:

readonly valueChanges: Observable<ApolloQueryResult<TData>>;

but when enabling intial loading, the data field in the result becomes nullable, which is not reflected in the type.

To Reproduce

1. Enable initialLoading in the config
2. Add a query similar to the following:

  private someQueryRef = this.apollo.watchQuery({
    query: SomeQueryDocument,
  });
  protected tests$ = this.testsRef.valueChanges.pipe(
    filter((result) => result.data != null),
    map((result) => {
      return result.data.someQuery;
    }),
  );

Typescript Eslint will come up with the error @typescript-eslint/no-unnecessary-condition on filter((result) => result.data != null). However, when removing the filter statement, you will get a TypeError: result.data is undefined error. Or am I misinterpreting something?

Expected behavior

The type of data is nullable when initial loading is enabled.

Environment:

├── @angular/cli@18.2.7 -> ./node_modules/.pnpm/@angular+cli@18.2.7_chokidar@3.6.0/node_modules/@angular/cli
├── @angular/core@18.2.7 -> ./node_modules/.pnpm/@angular+core@18.2.7_rxjs@7.8.1_zone.js@0.14.10/node_modules/@angular/core
├── @apollo/client@3.13.5 -> ./node_modules/.pnpm/@apollo+client@3.13.5_@types+react@18.3.3_graphql-ws@5.16.0_graphql@16.9.0__graphql@16._e3a29df517fd676fd5c435d43766e066/node_modules/@apollo/client
├── apollo-angular@10.0.3 -> ./node_modules/.pnpm/apollo-angular@10.0.3_@angular+core@18.2.7_rxjs@7.8.1_zone.js@0.14.10__@apollo+client@3_e1fef8ba11273a8ad1c04e01fcd397a5/node_modules/apollo-angular
├── graphql@16.9.0 -> ./node_modules/.pnpm/graphql@16.9.0/node_modules/graphql
└── typescript@5.5.4 -> ./node_modules/.pnpm/typescript@5.5.4/node_modules/typescript

[PowerKiKi]

I think there might be a misunderstanding somewhere. Please create a minimal reproduction case, on https://stackblitz.com (or similar) that proves something is wrong with apollo-angular and that is is not wrong with @apollo/client.