Skip to content
ContractSpec
Start here

UI · Intermediate · source walkthrough

Build a table from a data view

Compare a declarative account table with the shared client and server controller surfaces.

@lssm-tech/example.data-grid-showcase · Preview source inspected · evidence as of 2026-10-27

Source context

Preview source inspected · b67c376f

Pinned source links require repository access; publication and anonymous package availability were not checked for this example.

The same sample account grid appears through ContractSpec's data-view, headless table, web primitive, and design-system layers. You can inspect how sorting, selection, expansion, loading, and empty states are represented without adopting a whole business template.

What you will learn

  • Connect a table specification to a query contract.
  • Express initial sorting, page size, hidden columns, and pinned columns declaratively.
  • Separate a table controller mode from evidence about a real backend.

AN INTERACTIVE READING MAP

Walk through this example.

Step through the maintained source review, inspect its evidence boundaries, or assemble an adaptation packet.

SOURCE WALKTHROUGH

Read the operation in its authored order

01 / IN FOCUS

Start with the declarative table

The README's DataViewSpec references a sample query and declares a table view. Its initial state uses four rows per page, descending ARR sorting, a hidden notes column, and the account column pinned left.

1 / 4

0 points in your packet

Walk through the source

  1. Start with the declarative table. The README's DataViewSpec references a sample query and declares a table view. Its initial state uses four rows per page, descending ARR sorting, a hidden notes column, and the account column pinned left.
  2. Compare rendering layers. The showcase exposes client, server, DataView, web primitive, and native primitive lanes around the same account data. Inspect how each layer maps the shared table behavior.
  3. Explore visible states. The UI source includes pinning, sorting, row expansion, simulated loading, empty state, and an interaction log. Its smoke fixture checks rendering and selected interactions.
  4. Adapt the source contract. Replace sample account fields and the query reference with your own data contract. Establish server filtering, pagination, authorization, and performance behavior in your host application.

What this review establishes

  • The source includes a declarative table contract and a shared account-grid showcase.
  • The inspected smoke fixture asserts key UI controls, descending sort state, expansion, and row-press logging.
  • The generated registry declares an inline UI preview for data-grid-showcase.

Not established

  • Server throughput or database performance.
  • A live production dataset or backend integration.
  • A newly verified browser session in this review; the preview registration is source evidence.

Before adapting

  • Access to the inspected source repository and a checkout at the cited revision.
  • The repository's Bun workspace dependencies and required generated package exports. These instructions were inspected; the examples were not executed in this review.

Adapt the pattern

  • Begin with one query and one table before adopting a full template.
  • Map query results to explicit field data paths.
  • Test the remote data path independently from local controller interactions.
declaredStability
experimental
registry
Registered; deliberately not template-eligible
inlinePreview
Registered
execution
Not rerun
production
Not assessed