Skip to content

refactor(lokee): slim table timeline inspector and revert helpers - #249

Merged
huyplb merged 1 commit into
mainfrom
cursor/history-table-timeline-revert-847b
Aug 13, 2026
Merged

refactor(lokee): slim table timeline inspector and revert helpers#249
huyplb merged 1 commit into
mainfrom
cursor/history-table-timeline-revert-847b

Conversation

@huyplb

@huyplb huyplb commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Why

Follow-up to #248. The first pass worked, but the inspector, inspect payload, and revert helpers were heavier than they needed to be.

What changed

  • One timeline. Column mutations live inside Change timeline. Table-level ADD is not shown twice.
  • No extra HEAD fields. Last growth row is HEAD; inspect no longer returns headVersionId / headVersionNumber.
  • Revert UI. One revert state object + a small RevertCard, instead of five useStates and nested JSX.
  • Hydrate reuses isLokeeContainerType from blueprint.
  • planRevert / routes drop the copy-paste publish helper; routes strip steps with destructure.

Net −97 lines, same behavior. tsc --noEmit clean; Lokee unit tests green.

How to try it

Same as #248: History → click a table → growth v1…vN, column mutations, Revert on a prior version.

Open in Web Open in Cursor 

Drop the extra HEAD fields from inspect (last growth row is HEAD), merge
column mutations into the single change timeline, and collapse revert UI
state into one object. Hydrate reuses the blueprint container check;
planRevert and the revert routes share less boilerplate.

Co-authored-by: huy.phan9 <huyplb@users.noreply.github.com>
@huyplb
huyplb marked this pull request as ready for review August 13, 2026 07:24
@huyplb
huyplb merged commit 12a5bc0 into main Aug 13, 2026
10 checks passed
@huyplb
huyplb deleted the cursor/history-table-timeline-revert-847b branch August 13, 2026 07:24
@cursor

cursor Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_656e7b0b-cdbc-4028-8400-f705bda12ed7)

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.

2 participants