Skip to content

Conversation

@lawrence-forooghian
Copy link
Collaborator

Written by Claude based on JS at ably/ably-js@194aed7 (i.e. the commit into which path-based API was merged in ably/ably-js@a9aea33).

Note: There are two commits here. The first contains an direct translation of the JS code, the second is functionally equivalent but IMO easier to understand. See which you prefer (my preference is the latter) and I'll then rebase accordingly.

Written by Claude based on JS at 194aed7 (i.e. the commit into which the
path-based API was merged in a9aea33).
@lawrence-forooghian lawrence-forooghian force-pushed the AIT-255-fix-replace-data-events branch from ae32ba3 to 3f86319 Compare January 16, 2026 11:32
lawrence-forooghian added a commit to ably/ably-liveobjects-swift-plugin that referenced this pull request Jan 16, 2026
This implements the changes spec from [1] at 3f86319. That is, the
update events emitted by a sync are now calculated from the before/after
diff of the object state, as opposed to just being calculated from the
createOp.

Written by Claude based on the spec.

[1] ably/specification#414
lawrence-forooghian added a commit to ably/ably-liveobjects-swift-plugin that referenced this pull request Jan 16, 2026
This implements the spec changes from [1] at 3f86319. That is, the
update events emitted by a sync are now calculated from the before/after
diff of the object state, as opposed to just being calculated from the
createOp.

Written by Claude based on the spec.

[1] ably/specification#414
lawrence-forooghian added a commit to ably/ably-liveobjects-swift-plugin that referenced this pull request Jan 16, 2026
This implements the spec changes from [1] at 3f86319. That is, the
update events emitted by a sync are now calculated from the before/after
diff of the object state, as opposed to just being calculated from the
createOp.

Written by Claude based on the spec.

[1] ably/specification#414
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants