Conversation
…d 'no-shadow' with the 'queryKey' import
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughLocal variable Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit 9a550a1
☁️ 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 📦
|
🎯 Changes
Renames local
queryKeyvariables inside the type-level tests tokey, matching the convention used elsewhere in this file (const key = queryKey()) and across the rest of the test suite. This resolves the 10no-shadowwarnings previously triggered because thequeryKeyimported from@tanstack/query-test-utilswas shadowed by these local declarations.Scope
Only
describe('getQueryData', ...)anddescribe('setQueryData', ...)are affected — 10 localconst queryKey = [...]declarations becomeconst key = [...]. The existingconst key = queryKey()usages indescribe('fetchInfiniteQuery', ...)are already correct and are left untouched.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit