Consume the Atomic table package with native NextGraph views and schema workflows #80
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "investigate/atomic-table-port"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ELFA now consumes AtomicServer’s table grid and primitive editors as a package, rather than keeping a copied implementation. The upstream extraction is ontola/atomic-server#2434, with its own package CI lane. AtomicServer resolves the workspace from source; ELFA installs the compiled archive through pnpm.
The checked-in archive is an unpublished preview, pinned to upstream commit
3c86288f1ea8cac3a73d8ec1e8a47c95833ae763with SHA-256 and reproduction instructions in vendor-packages. Replace the file dependency with a registry version after the package’s first release. No npm release was performed.Behavior
wherefor collection membership and case-sensitive exact title filters,orderByfor raw primary sorting, andpageSize: 100/maxActivePages: 1with SDK next/previous navigation. There is no SPARQL table selection or subject-window fan-out. Alpha and Beta share one class to exercise collection isolation.The grid displays the current SDK window rather than invented page numbers or total/end cursors. Navigation is a no-op at either end; Refresh reopens the first page. Switching saved views reopens their ORM query. Large-table query planning/performance remains upstream. Lower-level document-pointer discovery/conditional publication remains separate metadata plumbing because the ORM has no publish-if-absent primitive.
The experimental runner keeps native storage, navigation, view and schema adapters in ELFA. The upstream package currently covers the grid and primitive editors; the full TablePage and upstream view-tab UI remain follow-up work.
Try
pnpm db-app-runner db-table-editor-portwith the normal local wallet/broker setup. Implementation, reproduction and limits.Validation
Limits and follow-up
Native reads/writes are verified within one running verifier. An attempted offline-wallet restart failed to reopen its native graph subscription; port-specific broker-backed restart and peer transport remain unexecuted. Distinct-user permissions, sharing of separate schema/view YMaps and collaboration remain unverified.
Advanced filters/aggregates, paste/undo, alternative renderers, derived columns/actions, links/uploads, comments/presence, preferred initial-view persistence, upstream view-tab extraction and 1k/10k/100k performance gates remain follow-up slices. Unsaved drafts/settings are session-local. New-document races may leave an unlinked YMap; no cross-document atomic transaction is claimed. Iframe custom views remain #78. Related to #77; this does not close the full-port investigation.
Screenshots
Assess full Atomic table port to ELFA Tablesto WIP: Assess full Atomic table port to ELFA TablesWIP: Assess full Atomic table port to ELFA Tablesto WIP: Port Atomic grid and typed editors to native NextGraphWIP: Port Atomic grid and typed editors to native NextGraphto WIP: Port Atomic grid, native saved views and schema workflows to NextGraphWIP: Port Atomic grid, native saved views and schema workflows to NextGraphto WIP: Consume the Atomic table package with native NextGraph views and schema workflowsWIP: Consume the Atomic table package with native NextGraph views and schema workflowsto Consume the Atomic table package with native NextGraph views and schema workflows