fix: pagination reset after saving a group - #79
Conversation
…le, and label editing
…and WhatsappGroupsPage
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (6)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe change adds shared group action buttons, replaces inline table controls, removes row-level label editing, preserves pagination after row-count changes, and updates related action styling. ChangesGroup table actions
Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The pagination and action-control updates do not show an actionable current risk. 🚥 Pre-merge checks | ✅ 2 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (2 passed)
Full details: Out of Scope Changes checkExplanation The pull request includes unrelated UI changes, including new shared action components, action redesigns, removal of row-level editing, users-table styling, and dialog-trigger styling. These changes are not required by issue
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
router.invalidate()reloads the route data with a new array reference on every save, which previously triggered TanStack Table's default pagination reset even though the row count hadn't changed.autoResetPageIndex: falseon all three group tables (Telegram, WhatsApp, combined) and clamps the current page back only when the row count actually shrinks past it (e.g. filtering/search), instead of always jumping to page 1.src/components/group-action-buttons.tsxto remove duplicated JSX.closes #78