fix: render persisted data in Suspense after client stream errors #1960
Merged
KyleAMathews(GitHub profile, opens in a new tab)merged 5 commits into
main fromrefs/pull/1960/head·merged by KyleAMathews(GitHub profile, opens in a new tab) Showing 8 changed files with 17 additions and 4 deletions (loading 5).
x
@@ -0,0 +1,6 @@
+---
+'@tanstack/db': patch
+'@tanstack/react-db': patch
+---
+
+Render completed persisted query data when a client query stream fails during network-first initial rendering. Keep derived-query load failures on the React ErrorBoundary, with errors isolated by client and cleared when the Collection restarts.
@@ -43,7 +43,7 @@
-| network-first initial render | An opt-in Suspense gate that prefers Collection readiness until a configured deadline or network failure, then permits a completed persisted restore. It does not stop network sync. | The persisted-readiness status itself or a change to ordinary live-query row publication. |
+| network-first initial render | An opt-in Suspense gate that prefers Collection readiness until a configured deadline or network failure, then permits a completed persisted restore. A failed client query stream counts as network failure; a failed derived query does not. The gate does not stop network sync. | The persisted-readiness status itself or a change to ordinary live-query row publication. |
@@ -522,13 +522,20 @@