-
Notifications
You must be signed in to change notification settings - Fork 140
Fix useLiveQuery loading status in on-demand sync #962
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.
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
base: main
Are you sure you want to change the base?
Fix useLiveQuery loading status in on-demand sync #962
Conversation
…sync For live queries using on-demand sync mode, the collection was being marked as ready immediately when source collections were ready, even though the initial loadSubset hadn't completed yet. This meant `isLoading` was false while data was still being fetched. This fix ensures that: 1. Live queries with on-demand sources track the initial loadSubset promise and show `isLoading: true` until it completes 2. The collection status remains `loading` until the first data load finishes 3. Subsequent loadSubset calls (pagination/windowing) do NOT affect the ready status - only the first load matters Changes: - Add `hasMarkedReady` and `hasSetupLoadingListener` flags to track initial ready state in CollectionConfigBuilder - Modify `updateLiveQueryStatus()` to wait for first loadSubset to complete before calling `markReady()` - Update `subscribeToMatchingChanges()` in CollectionSubscriber to track the initial loadSubset promise for on-demand sources - Add comprehensive tests for the new behavior
🦋 Changeset detectedLatest commit: 99f9cef The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
More templates
@tanstack/angular-db
@tanstack/db
@tanstack/db-ivm
@tanstack/electric-db-collection
@tanstack/offline-transactions
@tanstack/powersync-db-collection
@tanstack/query-db-collection
@tanstack/react-db
@tanstack/rxdb-db-collection
@tanstack/solid-db
@tanstack/svelte-db
@tanstack/trailbase-db-collection
@tanstack/vue-db
commit: |
|
Size Change: +182 B (+0.21%) Total Size: 88.7 kB
ℹ️ View Unchanged
|
|
Size Change: 0 B Total Size: 3.35 kB ℹ️ View Unchanged
|
Update test to wait for the initial loadSubset promise to resolve before checking the live query status. This is needed after the fix that makes live queries show loading status during initial on-demand data fetch.
…romise: true For on-demand sync mode, the default includeInitialState path calls requestSnapshot with trackLoadSubsetPromise: false, which doesn't track the loading state. This change manually calls requestSnapshot with trackLoadSubsetPromise: true for on-demand sources to ensure the subscription status changes from 'loadingSubset' to 'ready' when data arrives. Also updates query-db-collection tests to use eager mode since they test TanStack Query cache behavior, not on-demand loading status.
samwillis
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just a couple of things to tweak I think.
| // Set up a one-time listener if we haven't already | ||
| if (!this.hasSetupLoadingListener) { | ||
| this.hasSetupLoadingListener = true | ||
| const unsubscribe = this.liveQueryCollection.on( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should lift up the saved unsubscribe to save it at the top of the collection config builder level, then call it (if it exists) in the collection cleanup function. This is what we do with unsubscribeFromSchedulerClears - we should do the same as that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we add a test that checks this behaviour for an on-demand collection with a join to another on-demand collection. Check that it only modes to ready when both are not loading subsets.
…loading-status-01TNsEPERmfs3ub3e9iDRAzK
…DRAzK' of http://127.0.0.1:54067/git/TanStack/db into claude/fix-livequery-loading-status-01TNsEPERmfs3ub3e9iDRAzK
…eanup - Move loadingSubset listener unsubscribe to class property `unsubscribeFromLoadingListener` - Add cleanup call in sync cleanup function to prevent memory leaks - Add test verifying live query loading state tracks on-demand source loadSubset
Update react/todo and solid/todo examples to use ^1.0.8 to match other examples and pass sherif workspace version consistency check.
…DRAzK' of http://127.0.0.1:25666/git/TanStack/db into claude/fix-livequery-loading-status-01TNsEPERmfs3ub3e9iDRAzK
Verifies that when a live query joins two on-demand collections, the live query only becomes ready when BOTH sources have completed their loadSubset operations. Uses leftJoin to ensure predictable active/lazy source determination.
For live queries using on-demand sync mode, the collection was being marked as ready immediately when source collections were ready, even though the initial loadSubset hadn't completed yet. This meant
isLoadingwas false while data was still being fetched.This fix ensures that:
isLoading: trueuntil it completesloadinguntil the first data load finishesChanges:
hasMarkedReadyandhasSetupLoadingListenerflags to track initial ready state in CollectionConfigBuilderupdateLiveQueryStatus()to wait for first loadSubset to complete before callingmarkReady()subscribeToMatchingChanges()in CollectionSubscriber to track the initial loadSubset promise for on-demand sources🎯 Changes
✅ Checklist
pnpm test:pr.🚀 Release Impact