Proposed feature
The current Socket.io implementation validates each operation (addNode, updateNode, removeNode) individually against PostgreSQL. In concurrent editing scenarios, clients frequently drift out of sync — e.g., a client updates a node another client already deleted, causing FK constraint violations, full-map reloads, and degraded UX. Yjs eliminates these conflicts by design: concurrent changes merge deterministically without coordination.
This is an umbrella issue that captures all relevant PRs.
Proposed feature
The current Socket.io implementation validates each operation (addNode, updateNode, removeNode) individually against PostgreSQL. In concurrent editing scenarios, clients frequently drift out of sync — e.g., a client updates a node another client already deleted, causing FK constraint violations, full-map reloads, and degraded UX. Yjs eliminates these conflicts by design: concurrent changes merge deterministically without coordination.
This is an umbrella issue that captures all relevant PRs.