Repository navigation
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds four lines to the TanStack React framework docs explaining that the shared ChangesTanStack QueryClient Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
I don't have permission to add the required workflow labels on this repository. Suggested labels for this docs-only PR: \documentation, \ci:docs, \qa:skip. |
Summary
Closes #35283.
Adds clarification to the TanStack React framework docs explaining why the recommended TanStack Query setup uses one shared
QueryClientthat is cleared between stories.The new note also documents when a per-story
QueryClientcan be useful, especially for multiple stories rendered on the same Docs page with the same query keys, and calls out the tradeoffs around keeping the router context andQueryClientProviderwired to the same client.What changed
Testing
corepack yarn install --immutable --mode=skip-buildcorepack yarn fmt:writecorepack yarn docs:checkManual testing
Docs-only change. Manually reviewed the rendered Markdown source around the TanStack Query section to confirm the new guidance appears after the setup snippet and before the per-story seeding example.