useTableState: A reusable hook for server-side table state management

[NSTKrishna]

Current Behavior

Across Meshery UI, every data table page independently declares the same set of useState calls to manage server-side pagination, search, and sort state — typically page, pageSize, search, and sortOrder. Some pages add filter state on top. This results in 4–8 identical useState lines duplicated across 8+ files :-

• https://github.com/meshery/meshery/blob/master/ui/components/dashboard/resources/resources-table.tsx
• https://github.com/meshery/meshery/blob/master/ui/components/connections/meshSync/index.tsx
• https://github.com/meshery/meshery/blob/master/ui/components/performance/PerformanceProfiles.tsx
• https://github.com/meshery/meshery/blob/master/ui/components/workspaces/index.tsx
• https://github.com/meshery/meshery/blob/master/ui/components/environments/index.tsx
• https://github.com/meshery/meshery/blob/master/ui/components/DatabaseSummary.tsx
• https://github.com/meshery/meshery/blob/master/ui/components/filters/Filters.tsx
• https://github.com/meshery/meshery/blob/master/ui/components/connections/ConnectionTable.tsx

Expected Behavior

A reusable, framework-agnostic useTableState hook in Sistent that:

• Manages page, pageSize, search, sortOrder, and optional custom filters state
• Provides setter functions (setPage, setPageSize, setSearch, setSortOrder)

Environment

---

Contributor Guides and Resources

• 🛠 Meshery Build & Release Strategy
• 📚 Instructions for contributing to documentation
  • Meshery documentation site and source
• 🎨 Wireframes and designs for Sistent site in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

[Salmaan-M]

@NSTKrishna can you assign me in this?

[KhushamBansal]

@NSTKrishna I am not sure if we we need to have this in sistent as this is not a UI component. @aabidsofi19 Could you please confirm?

[Salmaan-M]

@KhushamBansal I will wait for @aabidsofi19 comment before working on the fix.

[Salmaan-M]

Hi @NSTKrishna, just following up on this issue. Since there was a question about whether useTableState belongs in Sistent (raised by @KhushamBansal), could you please confirm the intended direction before I start implementing it? I'm happy to work on it once the architecture is clarified.