improvement(tables): restore column configuration UX

J1
2mo ago
+518-74

Summary

  • Remove column-name editing from the edit sidebar while keeping the create-column name field
  • Rename plain and enrichment columns by double-clicking their headers
  • Keep invalid names editable with required, format, length, duplicate, and server-error feedback
  • Serialize inline rename sessions and register undo history only after persistence succeeds
  • Reuse the shared clipboard helper for Copy Row ID

Stack

This PR contains the general table UX split out of #7105. It is stacked on the Reference column foundation only because Copy Row ID is introduced there. The parent and #7106 retain the previous edit-sidebar rename behavior; this PR owns the full migration to header renaming.

Type of Change

  • Improvement
  • Breaking change

Testing

  • bun run --cwd apps/sim type-check
  • bunx biome check apps/sim
  • 5 focused sidebar, header, rename-lifecycle, and grid utility test files: 41 passing tests
  • Structured code review completed: run 20260902-132948-c71f26b6; all actionable findings applied and verified

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added or updated and passing
  • No new warnings introduced

Post-Deploy Monitoring & Validation

  • Search application logs for Error updating column in table and Failed to update column.
  • Watch error rate and latency for PATCH /api/table/:tableId/columns during the first 24 hours after deployment.
  • Healthy signals: single-click selects a column, double-click opens inline rename for plain/enrichment columns, workflow output columns remain protected, and successful renames create one usable undo entry.
  • Failure signals: stuck rename inputs, duplicate requests, a failed rename appearing in undo history, or elevated column-update errors. Revert #7390 while retaining the Reference foundation if these appear.
  • Validation owner: Tables team for the first 24 hours after deployment.