Skip to content

docs(feature-map): restore #563's Data Compare entry - #574

Merged
huyplb merged 1 commit into
mainfrom
docs/feature-map-datacompare
Nov 1, 2026
Merged

huyplb merged 1 commit into
mainfrom
docs/feature-map-datacompare

Conversation

@huyplb

@huyplb huyplb commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

#570 folded #563's hand edits to docs/feature-map.html into docs/feature-map/data.js, but missed the editor.datacompare row. The regenerated page lost:

  • subs: Compare 2,000 rows in key order, In-memory filters and pages, Apply up to 2,000 ops (one shared cap)
  • code: useCompareWindow, compareView.ts
  • tests: e2e sql-editor-compare-window

This puts them back in data.js and rebuilds the page with npm run docs:feature-map. The drift test (feature-map-build.test.ts) passes.

🤖 Generated with Claude Code


Note

Low Risk
Documentation and generated HTML only; no runtime or API behavior changes.

Overview
Restores editor.datacompare details in docs/feature-map/data.js that were dropped when an earlier merge moved the feature map into the shared data file without this row, then regenerates docs/feature-map.html.

The updated entry documents compare-window behavior (2,000 rows in key order, in-memory filters/paging, apply cap of 2,000 ops), points at useCompareWindow and compareView.ts, and lists e2e sql-editor-compare-window alongside the existing multi-target spec.

Reviewed by Cursor Bugbot for commit 8bed1fc. Bugbot is set up for automated code reviews on this repo. Configure here.

#570 moved #563's hand edits into the sources but missed the
editor.datacompare row, so the regenerated page dropped the 2,000-row
compare window, the shared op cap, useCompareWindow / compareView.ts
and the sql-editor-compare-window spec. Put them back in data.js and
rebuild.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@huyplb
huyplb merged commit 74660a6 into main Nov 1, 2026
12 checks passed
@huyplb
huyplb deleted the docs/feature-map-datacompare branch November 1, 2026 02:03
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