TS cache.readFragment could have a wrong type return

[albertcito]

The rePost variable has all the RePostFieldsFragment values:

const rePost = cache.readFragment(
  RePostFieldsFragmentDoc,
  { id: rePostID },
)

But the type says it only has id value o null

Looks like it's because this type:

readFragment<T = Data, V = Variables>(
  fragment: DocumentNode | TypedDocumentNode<T, V>, 
  entity: string | Data | T, 
  variables?: V
): T | null;

[kitten]

That seems normal depending on what you've passed in. Assuming that that document isn't typed then the default return value is Data which only guarantees the system fields of types. It's a little suspicious that it's incomplete but either you'll get Data, or if you're generating a typed fragment (which afaik no tool supports properly yet) you'll actually see your full type piped through

[albertcito]

Thank you @kitten.

I added the as with the return expected to the code and it works perfect:

const rePost = cache.readFragment(
  RePostFieldsFragmentDoc,
  { id: rePostID },
) as RePostFieldsFragment | null;

[lukasluecke]

Using a typed fragment actually works as expected, without any further type annotations (generated using the typed-document-node plugin in grapqhl-code-generator).