-
Notifications
You must be signed in to change notification settings - Fork 132
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
Open
KyleAMathews
wants to merge
4
commits into
main
Choose a base branch
from
claude/fix-livequery-loading-status-01TNsEPERmfs3ub3e9iDRAzK
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fix useLiveQuery loading status in on-demand sync #962
KyleAMathews
wants to merge
4
commits into
main
from
claude/fix-livequery-loading-status-01TNsEPERmfs3ub3e9iDRAzK
+278
−42
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…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: 3c50df6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 13 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: |
Contributor
|
Size Change: +163 B (+0.19%) Total Size: 87.3 kB
ℹ️ View Unchanged
|
Contributor
|
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.
Closed
…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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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