chore(solid-query-devtools/tsconfig): include 'test-setup.ts' for jest-dom matcher typings#10845
Conversation
|
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)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughReformats ChangesConfiguration formatting
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
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 unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit 1b96424
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview2 package(s) bumped directly, 23 bumped as dependents. 🟩 Patch bumps
|
size-limit report 📦
|
…t-dom matcher typings
1b96424 to
7dfda98
Compare
🎯 Changes
Add
"test-setup.ts"to theincludearray inpackages/solid-query-devtools/tsconfig.jsonso the@testing-library/jest-dom/vitesttype augmentation is picked up by the TypeScript compiler.Today, the file is loaded at runtime via
vite.config.ts'stest.setupFiles, so jest-dom matchers work in tests. However, because the file is not part of the TypeScript project, matchers liketoHaveStyle,toBeInTheDocument, andtoHaveClassare not recognized by the type checker and require workarounds such asas HTMLElementcasts.All other devtools/query packages that use a
test-setup.tsalready include it in their tsconfig (query-devtools,react-query-devtools,preact-query-devtools,solid-query,react-query,preact-query, etc.). This bringssolid-query-devtoolsin line with that convention.✅ Checklist
🚀 Release Impact
Summary by CodeRabbit