Package-level declarations
Functions
The outcome of a write the server applied, as a test double of the app's own returns it.
A Storage object held in the file cache, as the offline bucket reports one.
The failure of a read that may use only the cache and found nothing there.
Keeps the plugin's local data in memory, for tests: the cache, the mutation queue and the Storage file cache live in the client, and nothing is written to disk. Every other setting applies as it does in an app, so a test builds its client exactly as production does:
The failure of a write the mutation queue could not hold, sent at once and refused for want of a connection.
The failure of a request asked for while the app had turned the library's network access off.
A write waiting in the mutation queue, as Offline.pendingMutations lists one.
One emission of a reactive read, as selectAsFlow hands one out.
The outcome of a write that waits in the mutation queue.
A queued write the server refused for good, as Offline.rejectedMutations lists one.
What the server answered when it refused a write.
The state of a refresh that keeps failing.
Why a sync pass stopped with writes still queued, as SyncStatus.lastSyncError reports it.
What a call of Offline.syncPendingMutations did.
Where the library stands with the queue and the network, as Offline.syncStatus holds it; every field defaults to the state of a client that has done nothing yet.