Skip to content

Table editor optimization - #1499

Draft
kasbah wants to merge 6 commits into
mainfrom
kb/table-editor-optimization
Draft

kasbah wants to merge 6 commits into
mainfrom
kb/table-editor-optimization

Conversation

@kasbah

@kasbah kasbah commented Sep 14, 2026

Copy link
Copy Markdown
Member

No description provided.

@kasbah kasbah changed the title Kb/table editor optimization Table editor optimization Sep 14, 2026
@kasbah
kasbah force-pushed the kb/table-editor-optimization branch 4 times, most recently from d215d64 to 332f287 Compare September 16, 2026 09:54
Index tables, rows, and issues so lookups are constant time and per-row
issue entries keep their identity when unchanged. Each referenced table
gets its own memo so cells only react to the table they reference. Track
selection and editing state as cell keys via selectors so only affected
cells re-render, and memoize per-cell derived state so unchanged DOM
attributes are not rewritten. Show committed field values optimistically
until the row snapshot catches up or the returned promise settles; the
instance editor returns the write promise so the editor can observe it.
…dations.

Tables and rows are now plain snapshots of the document at validation time
rather than lazy views reading the store on every access. Unchanged tables,
rows, and issues keep their identity across validations so consumers can
skip work for unaffected parts; the instance editor uses this to hand each
table editor a stable issue list. Validation is cached per revision and
re-run when the schema validates. Stores may expose `untracked` so
validation, which is already tracked by revision, does not subscribe to
fine-grained document reads; the API store also skips the reactive proxy
while untracked.
@kasbah
kasbah force-pushed the kb/table-editor-optimization branch from 332f287 to bb377b7 Compare September 16, 2026 13:50

This branch was successfully deployed

1 active deployment
netlify-preview ead3a63a Deployed Sep 16, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant