WIP: Port Atomic views into three NextGraph ELFA database apps #67
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/elfa-app-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?
Superseded by the requested per-app split: #69 (preparation and README), #70 (ELFA Tables), #71 (ELFA Forms), #72 (ELFA Project). The original branch is preserved.
WP6 needs three NextGraph-based ELFA apps that reuse the Atomic Data Browser work. This initial port adds ELFA Tables, Forms and Project entry points over the existing shared collection/table pipeline.
Tables supports the shared grid plus card/calendar views. Project adapts select-field Kanban grouping and issue close/reopen behavior. Forms reuses the upstream storage-independent React renderer, with a basic builder and validated submissions into the same NextGraph table. Definitions use discrete documents; records use native RDF ORM subscriptions. There is no Atomic storage bridge.
The upstream source is pinned and MIT attribution retained. The original template-table app now uses the shared workspace. Existing exploratory apps remain in place.
This is a draft, not complete D6.2 delivery. Remaining work includes full builder/schema evolution, comments, board ordering, public/anonymous access, bounded alternative-view queries, ELFA shell/design alignment and native multi-user/restart testing. See docs/elfa-app-port.md.
Validation: 373 unit/integration tests passed, plus the additional native form-verifier test; seven browser workflows passed; ELFA/runtime/Atomic/Joep typechecks and all three production builds passed. The new native test checks definition persistence, stale saves, response persistence and deduplicated retries. Browser tests use fixtures; no claim of complete cross-user/offline behavior.
Pull request closed