mirror of
https://github.com/rcourtman/Pulse.git
synced 2026-10-15 16:42:15 +00:00
rcourtman
348b731408
Until now, the same column (CPU/Memory/Disk) was aligned differently depending on which table it appeared in: Proxmox top tables defaulted to left, Docker/TrueNAS/vSphere/Kubernetes top tables used right, the shared workloads bottom table used center, and integer-count columns (VMs/CTs/Containers/Datastores/Desired/etc.) were a mix of right and center. The user's read: "complete hobbledy codge." Codify the rule once and for all. The new frontend-modern/src/features/platformPage/columnAlignment.ts defines five canonical column kinds with a documented align mapping and the rationale for each: - 'name' left primary identifier - 'text' left readable strings - 'metric-bar' center bar fills cell, label rides at fill edge - 'numeric-value' right units/digits line up for column scanning - 'badge' center pill/icon-only cells sharedPlatformPage exposes getPlatformTableHeadClassForKind() and getPlatformTableCellClassForKind() wrappers; every platform top table plus the Docker services table now consume these instead of passing literal align strings. The Proxmox host column model carries a kind field instead of a raw align so the same source of truth drives both the model file and the JSX. KubernetesClustersTable.tsx is intentionally not migrated in this commit: another agent has it staged in their working tree. The same migration applies once that lands; left for a follow-up. The WorkloadTableHeader (shared bottom guest-list table) is also unmigrated here. It center-aligns everything today, and changing it to canonical means flipping Uptime / Net I/O / Disk I/O from center to right across every guest list on every platform page — bigger visual blast radius, so it gets its own scoped commit next. A canonical-platform-audit rule and a CLAUDE.md/AGENTS.md note will follow in a third commit, so any future agent that writes a non-canonical align fails the pre-push hook rather than discovers the drift visually weeks later.