test(query-devtools/Devtools): add test for rendering an idle mutation row#10764
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)
📝 WalkthroughWalkthroughThis PR adds a test case to the devtools test suite that verifies idle mutations—mutations created in the cache but not yet executed—are correctly rendered in the mutations view after timer advancement. ChangesDevtools Mutations View Test
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 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 docstrings
🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit 12cb965
☁️ 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
Extend
Devtools.test.tsxwith a test that locks the mutations view's idle path — when auseMutationhook is mounted but has not been triggered yet, the mutation cache holds an idle entry whose row should still render (covering thecolor() === 'gray'branch ofgetObserverCountColorStyles).Added cases (
view toggle, 1):should render an idle mutation that has been built but not executed— switches to the mutations view, builds a mutation in the cache without callingexecute, and asserts the mutation row appears.✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit