Use the ORM React signal adapter instead of serializing table rows

michielbdejong commented

2026-10-19 14:28:18 +02:00

Owner

A single row edit currently triggers full-collection JSON serialization so the table projection can detect a change in its effect dependencies. The manual React render counter also duplicates the signal adapter already used by the ORM's own useShape hook.

useRuntimeShape now binds the existing subscription through useDeepSignal, and Projection depends on the adapter's changing data identity. This removes the row-collection snapshot and manual watcher/render counter. The graph/schema-aware subscription lifecycle, unpooled runtime-shape handling, error reporting, loading state and late-completion cleanup remain in place. The direct signal dependency is pinned to the exact version already used by the ORM; no SDK version is upgraded.

Related to #52. This removes its collection-serialization bottleneck; pagination, bounded rendering, relationship option construction and whole-collection Atomic ingestion remain outstanding. It complements #57's draft reconciliation and is based independently on current main.

Validation: frozen-lockfile installation, all 332 unit tests, six typechecks, all 12 production builds, and 28 browser tests across the Native, Atomic, Joep and template table apps passed. New coverage writes through distinct real ORM subscriptions against the browser test engine and checks incoming scalar edits, nested set additions/removals, and row creation/deletion. Existing coverage verifies local edits and runtime schema replacement. Broker-backed synchronization tests and large-collection benchmarks were not run.

A single row edit currently triggers full-collection JSON serialization so the table projection can detect a change in its effect dependencies. The manual React render counter also duplicates the signal adapter already used by the ORM's own `useShape` hook. `useRuntimeShape` now binds the existing subscription through `useDeepSignal`, and `Projection` depends on the adapter's changing data identity. This removes the row-collection snapshot and manual watcher/render counter. The graph/schema-aware subscription lifecycle, unpooled runtime-shape handling, error reporting, loading state and late-completion cleanup remain in place. The direct signal dependency is pinned to the exact version already used by the ORM; no SDK version is upgraded. Related to #52. This removes its collection-serialization bottleneck; pagination, bounded rendering, relationship option construction and whole-collection Atomic ingestion remain outstanding. It complements #57's draft reconciliation and is based independently on current main. Validation: frozen-lockfile installation, all 332 unit tests, six typechecks, all 12 production builds, and 28 browser tests across the Native, Atomic, Joep and template table apps passed. New coverage writes through distinct real ORM subscriptions against the browser test engine and checks incoming scalar edits, nested set additions/removals, and row creation/deletion. Existing coverage verifies local edits and runtime schema replacement. Broker-backed synchronization tests and large-collection benchmarks were not run.

michielbdejong added 1 commit

2026-10-19 14:28:18 +02:00

Use the deep signal React adapter for runtime projections fb81542e88

michielbdejong referenced this pull request

2026-10-19 14:28:29 +02:00

Bound native/shared table loading and rendering; replace full-collection change serialization #52

michielbdejong merged commit eee6b6d07e into main

2026-10-19 14:33:20 +02:00

michielbdejong referenced this pull request from a commit

2026-10-19 14:33:20 +02:00

Merge pull request 'Use the ORM React signal adapter instead of serializing table rows' (#58) from codex/deep-signal-react-bridge into main

Rows
Columns

Use the ORM React signal adapter instead of serializing table rows #58