Last reviewed: 2026-11-13
Pretable is a batteries-included, domain-neutral React data grid. Correctness, performance, and developer experience govern its roadmap. Financial-grade applications are a proving ground, not the product boundary.
- Performance and correctness are product features: every major capability gets an explicit complexity/memory budget, deterministic workload, and committed evidence.
- Pretable ships working grid behavior and UI, not interfaces alone.
- One canonical derived model governs rendering, focus, selection, editing, clipboard, accessibility, and virtualization.
- The grid remains finance-capable but domain-agnostic; applications own valuation, formulas, permissions, storage endpoints, and retention policy.
- Public state and protocols are versioned and migration-aware.
The aligned public-package baseline is 0.20.3. The shipped grid includes local
sorting and typed filtering, selection, keyboard navigation, copy and validated
bulk paste, typed asynchronous editing, column virtualization and layout,
configurable row grouping and aggregation, variable-height rows, and batched
streaming transactions. It also includes native number and canonical calendar-date
formatting, a configurable tool panel, replaceable UI components, and external
processing/window metadata for application-owned server data.
Canonical calendar dates shipped in 0.14.0 via
#480; the calendar-date design
is not pending implementation. The S8 PMS benchmark profile is implemented;
financial-planning workloads remain deferred. Package changelogs and generated
API reports are the source of truth for shipped behavior. The external-data
primitives do not yet constitute the complete remote/live row-model protocol
listed below.
See the current core changelog, React changelog, core API report, React API report, and committed comparative benchmark evidence.
Grand totals and summary rows are implemented in this development branch and
awaiting merge; they are not part of the shipped 0.20.3 baseline. The
approved design
covers independent filtered/all-input scopes, engine or keyed server authority,
headless leases, cached aggregates, and read-only summary rendering.
Preserve existing correctness, 60 Hz, zero-gap, and interaction-continuity gates while completing validation and release review. Package changelogs remain the source of truth for when the feature ships.
- Ship saved-view persistence: a versioned portable view document, migrations, schema reconciliation, browser-local storage, remote store adapter, and shared/personal view layers.
- Add a typed command foundation with atomic edit/paste batches, inverses, and bounded local undo/redo. Saved views precede command history.
These priorities replace the older financial field-schema and application UI track. Applications continue to own domain schemas and policy.
- Extend the existing external-processing and window primitives into a remote/live row model with bounded caching, typed query plans, cancellation, partial/stale/error state, and ordered resynchronization.
- Add revisioned mutations with command IDs, base revisions, optimistic and pessimistic execution, conflicts, rollback, retries, and resync.
- Develop domain-neutral analytical and manipulation features: pivot, drill-through, context actions, export, range editing, fill, and row creation/reordering. Applications own formulas and scenario semantics.
- Add provider-backed durable audit/version history, history UI, revert-as-new-command, redaction, retention hooks, and collaborative updates.
- Continue shared/personal configuration, capability-aware UI, tree data, localization, and accessibility hardening.
- A hosted Pretable backend or authentication system.
- Finance-domain valuation, formula, scenario, or permission policy.
- A chart, page-layout, or financial-application platform.
- Persistence of complete runtime grid snapshots.
Saved views → command foundation and local undo/redo → revisioned mutations → durable audit/version history.
See the approved persistence and history design and its documentation implementation plan.
An item moves into implementation only after an approved focused design and implementation plan. It is complete only when public API reports, consumer documentation, correctness tests, and relevant benchmark evidence agree with the released behavior. The roadmap tracks outcomes; changelogs track shipped work, and dated plans remain historical execution recipes.