test(svelte-query/{queryOptions,infiniteQueryOptions}): flatten test directories that don't require '.svelte' component files#10245
Conversation
…directories that don't require '.svelte' component files
|
|
View your CI Pipeline Execution ↗ for commit 5e13282
☁️ Nx Cloud last updated this comment at |
|
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 (4)
📝 WalkthroughWalkthroughTest files in the svelte-query package have their relative import paths updated from a two-level up path to a one-level up path. No functional or logic changes are introduced; this adjustment modifies only module resolution within test files. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
🎯 Changes
Move
queryOptionsandinfiniteQueryOptionstest files from subdirectories totests/root, since they don't require.sveltecomponent files.Other test directories (e.g.,
createMutation/,useMutationState/,useIsFetching/) need.sveltecomponent files because they usesetContext/getContextfor sharingQueryClientacross multiple hooks. These two directories only contain pure unit tests and type tests, so the subdirectory structure is unnecessary.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit