Follow-up: run the reusable editor against an actual Atomic Server backend #45
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
After the 20 October demo and review fixes, add a real Atomic backend using the shared table record/schema boundary. NextGraph-backed Atomic Resources and an in-memory Atomic lib demonstration do not prove Atomic Server persistence.
Investigate the existing Atomic interfaces first. Define connection/agent selection, native Resource save/create, subscriptions/external edits, schema publication and supported constraints. Demonstrate the same table component against both backends and test error/draft behavior. Keep NextGraph-specific document/revision metadata behind its backend. No full SDK emulation is required. Preserve this as backlog rather than delay the 20 October milestone.
I think it's fine if we do this with an in-memory atomic store, since this is still just PoC phase. As long as we reason about other edits that may be incoming into that store.