Turntable

Simple, extendable data table focused on performance

Installation

Turntable can be installed with npm

npm install @turntable/core

or yarn

yarn add @turntable/core

Usage

1const columns = [
2  { value: "Name" },
3  { value: "Phone" },
4  { value: "City" },
5  { value: "State" }
6];
7
8const rows = [
9  {
10    cells: [
11      { value: "Julianne Littel" },
12      { value: "189-242-5961" },
13      { value: "South Sventown" },
14      { value: "Idaho" }
15    ],
16    position: 0,
17    rowIndex: 1
18  },
19  {
20    cells: [
21      { value: "Adela Skiles" },
22      { value: "582-187-2342" },
23      { value: "East Keegan" },
24      { value: "Delaware" }
25    ],
26    position: 1,
27    rowIndex: 2
28  },
29  {
30    cells: [
31      { value: "Naomie Dach" },
32      { value: "766-231-5964" },
33      { value: "Port Mackville" },
34      { value: "Missouri" }
35    ],
36    position: 2,
37    rowIndex: 3
38  },
39  {
40    cells: [
41      { value: "Dr. Corine Hirthe" },
42      { value: "327-913-2735" },
43      { value: "Lake Freder" },
44      { value: "Alabama" }
45    ],
46    position: 3,
47    rowIndex: 4
48  }
49];
50
51<Table
52  columnConfig={columns}
53  count={4}
54  initData={rows}
55  visibleRows={4}
56  rowHeight={40}
57/>

Developing locally

The app development environment can be started via one of two ways: NPM or Docker. Docker offers the additional ability to test package distributions locally.

Using NPM

Starting the app locally: npm run start

Watch types: npm run type-check:watch

Testing the app: npm run test

Starting Storybook: npm run storybook

Building: npm run build

Using Docker

Starting the app: docker-compose up dev

Testing the app: docker-compose run --rm dev npm run test

Watch types: docker-compose run --rm dev npm run type-check:watch

Starting Storybook: docker-compose up storybook

Test package in sandbox: docker-compose up pack

Versioning & Publishing Packages

Warning

Do NOT publish packages manually from your local environment. This will confuse the automation and make sadness.

Package publishing is automated through changeset and github workflows. To instigate publication:

1. Make a change to a package
2. Run npm run changeset, choose the package(s) that were modified, and follow instructions to fill out changelog details
3. Push the resulting .changeset file along with the package changes from the first step
4. Create PR with these changes and merge into main

This will trigger a github action to create a new PR with the increased version and changelog. Once this PR gets merged, CI runs again and releases the package(s) to npm.