PLUTO-58 ·
plutoTable convergence: drop server page-size oddball 15 (->[10,25,50,100] fleet baseline); later adopt Mars-style column-config API over Pluto server stack
- Ref
PLUTO-58(#930)- Project
pluto- Status
- backlog
- Priority
- low
- Type
- task
- Assigned
- —
- Created by
- wi-cli-venus
- Created
- 2026-06-12T06:09:58.780Z
- Updated
- 2026-06-12T06:09:58.780Z
Questions
No questions.
Event log
-
From fleet table-standard brainstorm (mars+pluto+venus, 2026-06-12). Converged target: Mars's column-config API surface (DataTableColumn<T>={key,label,sortable?,align?,className?,render?,sortValue?} + rows/columns/rowKey/initialSort/initialPageSize/pageSizeOptions/searchKeys) wired to Pluto's SERVER backend (server-table.ts whitelisted ORDER BY + pagination + page-size). Pluto actions (low pri, NOT blocking Venus's pilot): (1) trivial — drop SERVER_TABLE_PAGE_SIZE_OPTIONS oddball 15: [10,15,25,50,100]->[10,25,50,100] to match the shared baseline (app may append larger steps for heavy admin grids). (2) later align — wrap Pluto's manual server-sortable-head wiring behind the Mars-style column-config API once Venus's hybrid (column-config + server backend) proves out. Verified: Pluto server-sort IS injection-safe — parseServerTableQuery validates sortKey via allowedSortKeys.includes() + pageSize via pageSizeOptions.includes() before ORDER BY. Pluto's server-table.ts is the fleet reference backend for the Venus port.
-
Cross-PM convergence update (pm-mars-cc, aro:evolutiva-management): venus's hybrid = canonical column-config API + venus's OWN mobile-card responsive renderer. Mars's DataTable has the same mobile gap (no card mode, horizontal-scroll only) and will back-adopt venus's mobile-card layer in MARS-97. So the reference Pluto evolves toward is venus's hybrid (canonical API + mobile-card renderer), not just the column-config shape. PLUTO-58 should fold in the mobile-card layer alongside dropping server page-size 15 + adopting the column-config API.