Revert the live data layer (next.21 + next.22) → 0.2.0-next.23 - #19
Merged
Conversation
This reverts commit 123d8c5.
Reverts next.21 (useEntity/LiveEntityStore) and next.22 (globalThis registry) — the id-ping + keyed-refetch architecture they optimize is being abandoned for private Broadcast channels with the row on the socket, which deletes the refetch hop instead of polishing it. Work preserved on preserve/live-entities; the reconciler half re-lands with the private-channel client. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts #18 and the next.22 registry fix. The id-ping + keyed-refetch architecture they optimize is being abandoned: every remote change still pays a full gateway HTTP hop before rendering, so observers never get V1-class latency. Direction is now private Broadcast channels (gateway-minted realtime tokens +
realtime.messagespolicy) with the row carried on the socket.nextdist-tag returns to the0.2.0-next.20surface (as0.2.0-next.23)preserve/live-entities— the merge-by-id reconciler + optimistic overlay re-land as the client half of the private-channel designlatest(0.1.1) untouched throughoutPlatform PR codehs/bool#566 is being closed unmerged for the same reason.
🤖 Generated with Claude Code