Add Load sample data to the native table port #86

Merged
michielbdejong merged 2 commits from codex/table-sample-data into main 2026-11-06 12:14:04 +01:00

Stacked on #85.

An empty port table offers little to try. Add a Load sample data button beside Add row, inserting 215 examples into the selected collection through the native ORM. The examples cover multiple pages, zero quantities, checked/unchecked booleans, varied dates, empty notes and missing optional values. Loading clears the title filter and selects ascending order.

Use fixed identities per class/collection and insert only missing examples, preserving existing rows and edited samples on repeat loads. Validate all candidates before writing, use one bounded set of known sample subjects, commit through an ORM transaction and confirm the inserted records with a separate read. Loading is disabled while row drafts exist. No schema replacement or SPARQL table-query path is added.

Clarify that this runner uses its own PortRow class, and document how to create rows: Add row creates immediately; Enter/a second click opens cell editing; Save drafts commits cell edits.

Validation: port typecheck, production build and all 12 native browser tests passed. The new scenarios start from an empty wallet and verify paging, exact filtering beyond page one, repeated loads preserving edits, existing user rows, collection isolation and row creation after loading. Desktop/mobile previews were captured and inspected.

Setup also refreshes an existing pnpm file-package snapshot with a forced frozen install and clears the generated runner Vite cache. This prevents missing exports such as ViewTab when an upstream commit changes without a package version/lockfile change. Verified by deliberately installing the former archive, reproducing the missing-export error, running setup, checking the restored export/cache removal, and passing real browser hydration/sample loading and port typecheck. Stop the dev server before setup and restart it afterward.

Stacked on #85. An empty port table offers little to try. Add a **Load sample data** button beside **Add row**, inserting 215 examples into the selected collection through the native ORM. The examples cover multiple pages, zero quantities, checked/unchecked booleans, varied dates, empty notes and missing optional values. Loading clears the title filter and selects ascending order. Use fixed identities per class/collection and insert only missing examples, preserving existing rows and edited samples on repeat loads. Validate all candidates before writing, use one bounded set of known sample subjects, commit through an ORM transaction and confirm the inserted records with a separate read. Loading is disabled while row drafts exist. No schema replacement or SPARQL table-query path is added. Clarify that this runner uses its own `PortRow` class, and document how to create rows: **Add row** creates immediately; Enter/a second click opens cell editing; **Save drafts** commits cell edits. Validation: port typecheck, production build and all 12 native browser tests passed. The new scenarios start from an empty wallet and verify paging, exact filtering beyond page one, repeated loads preserving edits, existing user rows, collection isolation and row creation after loading. Desktop/mobile previews were captured and inspected. Setup also refreshes an existing pnpm file-package snapshot with a forced frozen install and clears the generated runner Vite cache. This prevents missing exports such as `ViewTab` when an upstream commit changes without a package version/lockfile change. Verified by deliberately installing the former archive, reproducing the missing-export error, running setup, checking the restored export/cache removal, and passing real browser hydration/sample loading and port typecheck. Stop the dev server before setup and restart it afterward.
michielbdejong changed target branch from codex/table-view-tabs to main 2026-11-06 12:14:03 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ELFA/database-apps!86
No description provided.