InfiniteData<TPageData, TPageParam> class final Infinite queries

The data an infinite query holds: every page fetched so far, and the param each was fetched with.

An infinite query is an ordinary query whose data is an InfiniteData, so everything the cache does — garbage collection, invalidation, filters, getQueryData/setQueryData — works on it unchanged; only the fetch differs, looping over pages instead of calling one function once.

The two lists are the same length and in the same order: pages[i] was fetched with pageParams[i], and the constructor refuses anything else.

Treat the value as immutable. Every InfiniteData the library writes — a fetch result, a structurally shared refetch, a copyWith — holds two unmodifiable lists, so the value read back from the cache cannot be grown behind the observers' backs: getInfiniteQueryData(key)!.pages .add(…) throws UnsupportedError. To change the pages, write a new value with setQueryData (for example built with copyWith). The constructor wraps nothing: a const [...] literal is already unmodifiable, and a growable list handed in through initialData or setQueryData stays the caller's own until the next fetch replaces it.

When every page is a list, flatten gives all items in order:

final data = client.getInfiniteQueryData<List<Post>, int>(
  QueryKey(['feed']),
);
final posts = data?.flatten<Post>().toList() ?? const <Post>[];