Scope Atomic table rows by table parent and class #59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/issue-51-atomic-membership"
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?
Opening one Atomic table previously showed every loaded row of its Class, including rows belonging to other tables or no table.
AtomicTablenow opens an Atomic Table resource, reads its existingclasstypemetadata, and selects host-supplied collection members by both row Class andparent.New rows receive the selected table as parent. Ordinary field edits preserve parent and Class, and stale saves recheck membership before preparing the draft and again before persistence. The shared React table keeps an active draft visible when its record leaves the collection, reports the missing record, and refuses Save until it returns; Cancel dismisses it. The shared component still has no graph or parent selection logic.
/atomic-reusedemonstrates two tables sharing one Class in one Store, including excluded unparented/wrong-class rows, correctly parented creation, external arrivals, movement between tables, reclassification and deletion. Collection notifications discover unknown arrivals and update both views. Regression coverage preserves NextGraph's graph-plus-class membership without an Atomic parent requirement.The demo's collection source is explicitly a complete local dataset. Actual Atomic Server collection queries, paging, member fetching and invalidation/refresh remain #45; the adapter contract and Atomic lib collection API handoff are documented. Parent membership does not grant edit permission. These checks validate locally observed membership and do not add a server-side conditional commit (#54).
Validation on the updated branch:
Closes #51.