メニュー
Paginating reads relies on passing a Pagination object to a RequestDetails and having a remote Source which correctly applies its values to the network request.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Understand how sources declare operation capabilities via supportedOperations and how SourceList respects them.
FirestoreAdminSource connects google_cloud_firestore for server-side Dart applications to a SourceList.
FirestoreSource seamlessly connects Cloud Firestore streams to a SourceList.
Perform untyped Firestore document merges using the raw method on Firestore sources.
Cached data is mapped uniquely per request hash (RequestDetails with specific filter and pagination), supporting a powerful request-based caching behavior.
The SourceList class manages the delegation of read/write attempts to various configured Sources, with a read-thru cache system prioritizing local Sources.
| name | paginating-reads |
| description | Paginating reads relies on passing a Pagination object to a RequestDetails and having a remote Source which correctly applies its values to the network request. |
| metadata | {"last_modified":"Sat, 18 Apr 2026 1:52:50 GMT"} |
Paginating reads relies on configuring a RequestDetails object with a Pagination object and having a remote Source which correctly applies its values to the network request.
final details = RequestDetails(
pagination: Pagination.page(1, pageSize: 10),
);
// Load the first 10 users
final list = await userRepository.getItems(details);
Page-based pagination, or pure limit-offset pagination, can be activated by using the Pagination.page() convenience constructor.
Cursor-based pagination, or "start from here" pagination, can be activated by using the Pagination.cursor() convenience constructor.
In both scenarios, it is up to the remote Source to correctly apply this to the network request, and for the actual API at the end of the line to honor the pagination request.