Conversation
…to 'err' to avoid 'no-shadow' with outer 'error'
|
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)
📝 WalkthroughWalkthroughA callback parameter name in a Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 ac790a1
☁️ 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 the
throwOnErrorcallback parameter on line 6849 fromerrortoerrso it no longer shadows the outererrorreturned byuseQueryon line 6846. This resolves theno-shadowwarning and matches the convention already used elsewhere in this file:throwOnError: (err) => err.message !== 'Local Error'(line 2832, 2868)retry: (_failureCount, err) => err.message !== 'NoRetry'(line 3290)After this change, every error-callback parameter in
useQuery.test.tsxis namederr.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit