test(query-devtools/Explorer): add test for action buttons rendered inside a paginated page#10743
Conversation
…nside a paginated page
|
View your CI Pipeline Execution ↗ for commit 0c80f03
☁️ 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. |
|
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)
📝 WalkthroughWalkthroughAdded a test case to Explorer that constructs a 200-item paginated array, expands the explorer by default, and verifies that item-level "Remove all items" action buttons render correctly within the paginated page section. ChangesExplorer pagination action button test
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
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 |
size-limit report 📦
|
🎯 Changes
Extend
Explorer.test.tsxwith a test that locks the prop propagation from a parentExplorerto its paginated children — when a paginated page is opened, each child item should receiveactiveQueryandeditableso its action menu renders the same as a non-paginated child.Added cases (
pagination, 1):should render action buttons for items inside a paginated page— uses a 200-elementArray<Array<number>>so the parent paginates and each child is itself an array, then opens the first page and asserts that more than oneRemove all itemsbutton is rendered (one for the parent plus one per array child inside the page).✅ Checklist
pnpm run test:pr.🚀 Release Impact
Summary by CodeRabbit