Repository navigation
fix(query-core): honour fetchStatus filters in isFetching - #12281
vkpdeveloper wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: 8a05d5a The changes in this PR will be included in the next version bump. This PR includes changesets to release 24 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 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
🎯 Changes
Fixes #11984
QueryClient.isFetchingspreads the caller's filters and then always setsfetchStatus: 'fetching', so passingfetchStatus: 'paused'or'idle'is ignored. It now uses the givenfetchStatusand falls back to'fetching'only when none is given, so default counts don't change.useIsFetchingin every adapter just forwards filters, so they get the fix too; their doc comments and the generated reference docs are updated to match.New tests in
queryClient.test.tsxanduseIsFetching.test.tsxfail without the fix (paused count 0 instead of 1) and pass with it.test:prpasses except the Preact example typecheck, which fails on its own builtdistfolder and passes once that folder is removed.AI use: the code was written by gpt-6-astra (xhigh) in Codex CLI, and this description with Claude Code (Opus 5.5).
✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
🤖 Generated with Claude Code
Summary by CodeRabbit
New Features
fetching(the default),paused, oridle.Documentation