AppDataTable

Page-level data-table view: a header row (title + description and a toolbar), a bordered table surface, and an optional footer for pagination. Layout only — supply the actual table as children. Presentational and theme-driven.

Members

Manage who has access to the Acme workspace.

NameEmailRoleStatus
Ada Lovelaceada@acme.devOwner
active
Grace Hoppergrace@acme.devAdmin
active
Linus Torvaldslinus@acme.devMember
active
Margaret Hamiltonmargaret@acme.devAdmin
invited
Donald Knuthdonald@acme.devMember
suspended

Showing 5 of 5 members

Installation

pnpm
pnpm dlx @hex-core/cli add app-data-table

API Reference

PropTypeDefaultDescription
childrenrequired
ReactNodeThe table itself — typically a <DataTable> or <Table>.
title
ReactNodeSection title above the table.
description
ReactNodeOptional copy under the title.
toolbar
ReactNodeToolbar region (search field, filters, 'Add' button) aligned right of the title.
footer
ReactNodeFooter region under the table (pagination, row count).
className
stringAdditional classes applied to the root <section>.

AI Guidance

When to use

Use to frame a list/table page: a header with search and actions, the table, and pagination. Drop a DataTable or Table into children.

When not to use

Don't use it as the data grid itself — it's the frame; the table comes from the data-table or table component. Don't use for dashboards of metrics (use app-stats).

Common mistakes

  • Expecting sorting/filtering from this block — it's layout; that logic lives in the DataTable you pass as children.
  • Putting the page <h1> here when AppShell's header already has one — this title is a section <h2>.
  • Omitting a footer with pagination on long tables, leaving no way to page.

Accessibility

The section title renders as an <h2>. The block doesn't add table semantics — those come from the Table/DataTable in children. Toolbar controls should carry their own labels (e.g. a search input with an accessible name).

Token budget: 600