feat(Table): add renderRow prop to wrap data rows

[simplesagar]

What

Adds a renderRow prop to Table (and Table.Body): (row, rowElement) => ReactNode. The internal RowContainer now forwards refs and extra <tr> props, so the row element can back composition patterns like Radix ContextMenuTrigger asChild.

• Applies to plain, expandable (wraps the <tr> only, not the expanded panel), and grouped rows.
• No behavior change when the prop is omitted.

Why

The Gram dashboard is adding right-click context menus to all table rows with per-row actions (companion PR in speakeasy-api/gram). Moonshine's Table owns the <tr>, so consumers had no way to attach a context-menu trigger per row.

Testing

• New src/components/Table/index.test.tsx: wrapper runs per row, extra props (onContextMenu, data-testid) land on the <tr>, onRowClick still works when wrapped.
• New WithRenderRow story.
• pnpm type-check, pnpm lint, pnpm test (50/50), pnpm build all pass.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Mpze1EupifNgKSkWRZ8BZc

---

Summary by cubic

Adds a new renderRow prop to Table so consumers can wrap each <tr> (e.g., per‑row context menus) without changing behavior when unused. Works with sortable headers, expandable rows, and grouped rows.

• New Features
  • renderRow: (row, rowElement) => ReactNode on Table and Table.Body.
  • Applies to plain rows, expandable rows (wraps only the <tr>), and grouped rows; compatible with sorting.
  • RowContainer forwards refs and additional <tr> props; onRowClick remains supported when wrapped.

^{Written for commit f740151. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 3 files

Confidence score: 4/5

• In src/components/Table/index.test.tsx, renderRow is missing coverage for expandable and grouped row paths that the PR says are supported, so a regression in row structure/behavior could slip through and only show up at runtime for those table variants — add targeted tests for expandable-row wrapping and grouped-row rendering before (or immediately after) merge to de-risk this.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/components/Table/index.test.tsx">

<violation number="1" location="src/components/Table/index.test.tsx:203">
P2: Consider adding test coverage for `renderRow` with expandable rows and grouped rows. The PR description lists both as supported paths — expandable rows wrap only the `<tr>` (not the expanded panel) and grouped rows apply `renderRow` to each row inside the group — but the current tests only cover plain data rows. Adding a quick test for each would confirm the wrapping boundary and prevent regressions.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Fix all with cubic | Re-trigger cubic</sub>

[cubic-dev-ai]

P2: Consider adding test coverage for renderRow with expandable rows and grouped rows. The PR description lists both as supported paths — expandable rows wrap only the <tr> (not the expanded panel) and grouped rows apply renderRow to each row inside the group — but the current tests only cover plain data rows. Adding a quick test for each would confirm the wrapping boundary and prevent regressions.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/components/Table/index.test.tsx, line 203:

<comment>Consider adding test coverage for `renderRow` with expandable rows and grouped rows. The PR description lists both as supported paths — expandable rows wrap only the `<tr>` (not the expanded panel) and grouped rows apply `renderRow` to each row inside the group — but the current tests only cover plain data rows. Adding a quick test for each would confirm the wrapping boundary and prevent regressions.</comment>

<file context>
@@ -191,3 +192,52 @@ describe("Table sortable headers", () => {
+    expect(screen.getByText("go")).toBeTruthy();
+  });
+
+  it("wraps every data row and forwards extra props onto the <tr>", () => {
+    const onContextMenu = vi.fn((e: React.MouseEvent) => e.preventDefault());
+    render(
</file context>