Skip to content

React useQuery result includes fetchReason - #719

Open
mintlify[bot] wants to merge 1 commit into
mainfrom
autopilot/307ced05
Open

mintlify[bot] wants to merge 1 commit into
mainfrom
autopilot/307ced05

Conversation

@mintlify

@mintlify mintlify Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Release: Version Packages #1137. Source PR: React: Add fetchReason to the useQuery result. Found in release review.

Resolves #691

Released in @powersync/react 2.1.0.

  • client-sdks/frameworks/react.mdx: the useQuery hook description now lists fetchReason with its values. It also explains that 'settings-changed' means data still holds the previous query's rows. I checked this against FetchReason and the useQuery result types in @powersync/react 2.1.0: the values are 'initial' | 'refresh' | 'tables-changed' | 'settings-changed', and fetchReason is undefined when isFetching is false. The Vue hooks don't have this field, so I left the Vue page unchanged.

@bean1352, could you confirm this is accurate?

@mintlify
mintlify Bot requested a review from benitav October 22, 2026 13:12
@mintlify

mintlify Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
powersync 🟢 Ready View Preview Oct 22, 2026, 1:12 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

This branch was successfully deployed

1 active deployment
staging — 66660b3a Deployed Oct 22, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Divergence] React useQuery adds fetchReason to explain why isFetching is true (powersync-js #1141)

1 participant