feat(table): export Cell and HeaderCell components with their props definitions

[smmoosavi]

Summary by CodeRabbit

• New Features
  • Introduced Cell and HeaderCell components for building flexible table cells with custom content.
  • Added configurable props interfaces enabling control over cell behavior and appearance.
  • Extended the public API to allow developers to create custom table structures and layouts.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

These changes expose new table cell components (Cell and HeaderCell) to the public API by adding type definitions, source exports, and correcting the header cell props interface naming for consistency.

Changes

Cohort / File(s)	Summary
Type Definitions and Public Exports packages/ctablex-table/index.d.ts, packages/ctablex-table/src/index.ts	Added type declarations and source exports for Cell component with CellProps interface, and HeaderCell component with HeaderCellProps interface, extending the package's public API.
Component Implementation packages/ctablex-table/src/table/header-cell.tsx	Renamed CellProps interface to HeaderCellProps and updated HeaderCell function signature to use the renamed interface for clarity and consistency.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 New cells are born, both header and data,
Exported with pride, no regex to grate-a!
HeaderCellProps now wears its true name,
The table grows stronger, its API's the same! 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title accurately describes the main change: exporting Cell and HeaderCell components with their props definitions, which aligns with the changes in all affected files.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch export-cells

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (89a0579) to head (749b78b).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #10 +/- ##
=========================================
Coverage 100.00% 100.00% =========================================
Files 37 37 Lines 226 226 Branches 50 50 =========================================
Hits 226 226 

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/ctablex-table/index.d.ts (1)

57-64: Consider standardizing return types for consistency.

The type declarations for HeaderCell and HeaderCellProps are accurate. However, there's an inconsistency in return types across the file: Cell returns JSX_2.Element (lines 13) while HeaderCell returns ReactElement<any, string | JSXElementConstructor<any>>. While both are compatible, standardizing on one pattern (preferably JSX_2.Element) would improve consistency.

🔎 Optional refactor for consistency

-export declare function HeaderCell(- props: HeaderCellProps,-): ReactElement<any, string | JSXElementConstructor<any>>;+export declare function HeaderCell(props: HeaderCellProps): JSX_2.Element;

Note: This inconsistency exists for other components in the file as well (e.g., Table, TableBody, TableFooter use the verbose ReactElement form). Consider standardizing all component return types to JSX_2.Element for consistency.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 89a0579 and 749b78b.

📒 Files selected for processing (3)

• packages/ctablex-table/index.d.ts
• packages/ctablex-table/src/index.ts
• packages/ctablex-table/src/table/header-cell.tsx

🧰 Additional context used

🧬 Code graph analysis (2)

packages/ctablex-table/src/index.ts (2)

packages/ctablex-table/src/table/cell.tsx (2)

• Cell (11-21)
• CellProps (6-10)

packages/ctablex-table/src/columns/column.tsx (1)

• Column (17-28)

packages/ctablex-table/index.d.ts (4)

packages/ctablex-table/src/index.ts (4)

• Cell (25-25)
• CellProps (26-26)
• HeaderCell (28-28)
• HeaderCellProps (29-29)

packages/ctablex-table/src/table/cell.tsx (2)

• Cell (11-21)
• CellProps (6-10)

packages/ctablex-core/src/index.ts (1)

• Accessor (50-50)

packages/ctablex-table/src/table/header-cell.tsx (2)

• HeaderCell (9-13)
• HeaderCellProps (5-8)

🔇 Additional comments (3)

packages/ctablex-table/src/table/header-cell.tsx (1)

5-9: LGTM! Excellent renaming for clarity.

The rename from CellProps to HeaderCellProps prevents naming collision with the Cell component's props and improves code clarity. The component signature is consistently updated to use the new interface name.

packages/ctablex-table/src/index.ts (1)

25-29: LGTM! Exports follow established patterns.

The new exports for Cell, CellProps, HeaderCell, and HeaderCellProps are properly structured and consistent with the existing export pattern in the file. The placement and grouping are logical.

packages/ctablex-table/index.d.ts (1)

13-19: LGTM! Type declarations are accurate.

The type declarations for Cell and CellProps correctly reflect the implementation, with proper generic typing and optional properties matching the source code.