Skip to content

docs(persistence): remove stale on-demand initialRender restriction #2285

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KyleAMathews merged 1 commit into from
Oct 28, 2026
Merged

docs(persistence): remove stale on-demand initialRender restriction #2285

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/guides/sqlite-persistence.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -278,7 +278,7 @@ These rules keep `ready` meaningful:
- **A failed restore is a crash.** The Collection becomes `crashed`, because local storage cannot serve reads.
- **The deadline does not stop network sync.** Network changes apply over the restored rows when they arrive.

`initialRender` requires an eager persisted Collection. It does not support `syncMode: 'on-demand'`, which has no complete startup snapshot.
These rules apply to an eager Collection. An on-demand Collection applies `initialRender` to each query demand. See [On-demand Collections offline](#on-demand-collections-offline).

Suspense uses the same status. This React component uses the `syncedTodos` Collection configured above:

Expand Down
Loading