From 8be92f6c1c1fd2f92270ca0757ce9bb6719d6f42 Mon Sep 17 00:00:00 2001 From: Test Date: Wed, 28 Oct 2026 11:33:36 -0600 Subject: [PATCH] docs(persistence): remove stale on-demand initialRender restriction The guide said initialRender requires an eager Collection, which contradicted the on-demand section that #2263 added. Point the eager readiness rules at that section instead. Co-authored-by: Isaac --- docs/guides/sqlite-persistence.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/sqlite-persistence.md b/docs/guides/sqlite-persistence.md index 0ad929dbc4..feea3f9954 100644 --- a/docs/guides/sqlite-persistence.md +++ b/docs/guides/sqlite-persistence.md @@ -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: