Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: TanStack/query/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (4)
🚧 Files skipped from review as they are similar to previous changes (2)
Included review availability: Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe pull request updates React and Preact Query JSDoc and reference documentation. It clarifies ChangesQuery documentation updates
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Possibly related PRs
Suggested reviewers: Merge Risk: ⚪ Minimal · up to This update clarifies existing Query documentation and source links without changing runtime behavior or the public API, so it is ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
|
View your CI Pipeline Execution ↗ for commit e84f699
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version PreviewNo changeset entries found. Merging this PR will not cause a version bump for any packages. |
size-limit report 📦
|
…s' fallback JSDoc inaccuracies
…InitialDataOptions' JSDoc
🎯 Changes
Two JSDoc inaccuracies in
@tanstack/react-queryand@tanstack/preact-query(identical source structure in both packages):DefinedInitialDataOptions,DefinedInitialDataInfiniteOptions,DefinedUseQueryResult,DefinedUseInfiniteQueryResult, and the twouseQuery/queryOptionsoverloads selected wheninitialDatais set all stated thatdatais "neverundefined" without qualification. This is only true when noselectis used — aselectcan changeTDatato a type that includesundefined. Added the(unless a select changes TData to include undefined)qualifier, consistent with the existing@template TDatadoc on these types.QueriesOptionsandSuspenseQueriesOptions(thequeriesarray type foruseQueries/useSuspenseQueries) stated that only "a non-tuple array of a known element type, or a tuple past 20 elements" falls back to a single homogeneous options type. This conflated two different cases: a non-tuple array whose element type structurally matches a query options object is mapped per-element (not a fallback), while any other non-tuple array — one whose element type doesn't match the expected shape — does fall back, independent of the 20-element tuple limit. Reworded to separate these cases correctly, and split theQueriesOptions/SuspenseQueriesOptionsdoc comments into paragraphs for readability.✅ Checklist
pnpm run test:pr, or these tests do not apply to this pull request.🚀 Release Impact
Summary by CodeRabbit
undefinedafter aselecttransformation, including cases with initial data.