Demonstrate reusable React table controls with Atomic lib and a portable schema profile #43

New issue

Closed

opened 2026-10-15 13:33:53 +02:00 by michielbdejong · 0 comments

michielbdejong commented

2026-10-15 13:33:53 +02:00

Owner

The 20 October demo must show how the table editor can be reused on Atomic, not merely display an Atomic label over NextGraph storage.

Acceptance:

Reuse the same React table component for NextGraph records and actual @tomic/lib Store/Resource records.
Keep session, graph, useShape/useDiscrete and transport details outside that component, with a small typed record/schema boundary.
Exercise representative create/edit/validation and external updates through the Atomic library; retain drafts on failed saves.
Audit demo schema features against Atomic Schema/lib. Separate portable Class/Property/constraints metadata from NextGraph RDF mapping, document and revision metadata. Do not require a NextGraph-only concept in the common component.
Record pinned versions and any unpublished upstream compatibility helpers. A real Atomic Server transport/backend remains follow-up; no full NextGraph SDK polyfill.

Prefer existing SchemaTable and adapter code over a new table implementation. Rehearsal-ready Monday 19 October, demo Tuesday 20 October 2026.

The 20 October demo must show how the table editor can be reused on Atomic, not merely display an Atomic label over NextGraph storage. Acceptance: - Reuse the same React table component for NextGraph records and actual @tomic/lib Store/Resource records. - Keep session, graph, useShape/useDiscrete and transport details outside that component, with a small typed record/schema boundary. - Exercise representative create/edit/validation and external updates through the Atomic library; retain drafts on failed saves. - Audit demo schema features against Atomic Schema/lib. Separate portable Class/Property/constraints metadata from NextGraph RDF mapping, document and revision metadata. Do not require a NextGraph-only concept in the common component. - Record pinned versions and any unpublished upstream compatibility helpers. A real Atomic Server transport/backend remains follow-up; no full NextGraph SDK polyfill. Prefer existing SchemaTable and adapter code over a new table implementation. Rehearsal-ready Monday 19 October, demo Tuesday 20 October 2026.

michielbdejong referenced this issue from a pull request that will close it,

2026-10-15 13:46:17 +02:00

Prepare the 20 October table demo with same-document schemas and Atomic lib reuse #40

michielbdejong closed this issue

2026-10-15 15:44:42 +02:00

michielbdejong referenced this issue

2026-10-19 11:19:57 +02:00

Scope Atomic table rows by table parent and class instead of Store-wide class membership #51