yrby 0.2.0-aarch64-linux → 0.2.3-aarch64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3df6d0fa35fa727623994108610049d211940ca8d50adac0b3fd2f7fbaa8aa2b
-  data.tar.gz: e7ac7a5e9f2f01ea8af1a36eaff58eb6ffc86c14ff25d67a523373c4a69ce431
+  metadata.gz: e672475cdf4e8d6bee399365c00ca8059b192b9232767e5854a20988c7b7e629
+  data.tar.gz: 70ca13fb08dbdb54c96cdcc2c6dd5af31ef4af76af9896f15f4d17dddc4bb586
 SHA512:
-  metadata.gz: 428cb3117ef111a2ca5d211b356bc932b3c9116d0816dbcb35198649a687e1d26c8f1569e033fd8ff7fe417f6eef7e1171fc01ff77c6cb101b7e89f2771cd863
-  data.tar.gz: bc0d555eac46cb97748b4df45a4e44d1c003b9c65c7b0e14722ce3b1c89d10011b5483c09605f423f43252a4e8d1849085d77c3ed6298b58b6248ef63b4fbaa4
+  metadata.gz: 488c5e0a897958d514a5a31fd6ec488b31c84d9b54bc0ca625fdbe11a9b37e4df4102b97563316f957e4801a60f51997f7d326fb7df0e50aa6196c3e915a6408
+  data.tar.gz: 8b8d7de6765a87b218df2a3d57c541a6f678a73ed79bd6091c80b757bc2aee866fd8115d6e793d941d8665e5543ef58711ce5e014b5654899ce5a92a6d2f6c09

data/CHANGELOG.md

@@ -6,17 +6,56 @@ to follow [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
-## [0.2.0] - 2026-06-28
+## [0.2.3] - 2026-07-01
+
+### Fixed
+
+- `Doc#update_advances?` is now exact for **delete-bearing** updates, so an
+  already-applied pure-delete retry no longer reports as advancing. Previously any
+  update carrying a delete set returned `true` (record it) because deletes don't
+  move the state vector, so the cheap state-vector probe couldn't prove a
+  duplicate. A lost-ack retry of a deletion the server had already integrated was
+  therefore re-recorded and re-broadcast every time. For delete-bearing updates we
+  now compare the full encoded document state (which includes the delete set)
+  before vs. after a trial apply on an isolated probe: a genuinely new deletion
+  changes it (`true`); an already-applied retry re-encodes identically (`false`).
+  Insert/format-only updates keep the cheaper state-vector path, so only
+  delete-bearing frames — a minority — pay for the exact comparison. The exactly-
+  once guarantee is unchanged in the safe direction: a real deletion is never
+  dropped.
+
+  This lets `yrby-actioncable` (and any caller gating `on_change` on
+  `update_advances?`) settle a duplicate pure-delete frame as `:applied` — acked,
+  but not stored or relayed — so apps no longer need an app-level
+  encode-and-compare guard around their durable writes.
+
+## [0.2.2] - 2026-06-30
 
-First release under the **`yrby`** name (the project was previously developed
-as `yrb-lite`). The public Ruby interface is the top-level module **`Y`** —
-mirroring the `y-rb` gem's `Y::Doc` interface.
+### Fixed
+
+- `Doc#read_xml` now recovers text from **nested** Lexical/Lexxy blocks. Lexical
+  embeds child blocks (list items, table cells, nested lists) as `Y.XmlText`
+  embeds that `get_string` silently drops, so lists and tables previously came
+  back empty. `read_xml` now walks the embeds: text runs build a line, inline
+  children (links) join it, and nested block children flush and recurse — so a
+  document with headings, formatted text, links, bullet/numbered/check/nested
+  lists, blockquotes, code blocks and tables extracts every piece of text.
+  Lexical decorator elements (horizontal rule, image) are skipped instead of
+  emitting their `<UNDEFINED …>` serialization. ProseMirror handling is
+  unchanged.
+
+## [0.2.1] - 2026-06-29
 
 ### Changed
-- **Renamed `yrb-lite` → `yrby`.** Module `YrbLite` → top-level `Y`
-  (`Y::Doc`, `Y::Error`, `Y::VERSION`). Require path `require "yrb_lite"` →
-  `require "y"`. Native extension crate `yrb_lite` → `y_ruby`, loaded from
-  `lib/y/y_ruby.bundle`.
+- **Internal:** renamed the native extension crate `y_ruby` → `yrby` (now loads
+  from `lib/y/yrby.bundle`). No public API change — `require "y"` and `Y::Doc`
+  are unchanged.
+
+## [0.2.0] - 2026-06-28
+
+First release. The public Ruby interface is the top-level module **`Y`**
+(`Y::Doc`, `Y::Error`, `Y::VERSION`), loaded with `require "y"` — mirroring the
+`y-rb` gem's `Y::Doc` interface.
 
 ### Added
 - Native `Doc#read_text` and `Doc#read_map` readers — reconstruct plain text and

data/README.md

@@ -20,7 +20,7 @@ end
 ```
 
 On the browser, use the `ActionCableProvider` from the 
-[`@yrby/client`](https://www.npmjs.com/package/@yrby/client) npm package.
+[`yrby-client`](https://www.npmjs.com/package/yrby-client) npm package.
 Integrates with any editor that includes Y.js support, such as Tiptap, ProseMirror
 and [Lexxy](https://www.npmjs.com/package/lexxy-realtime).
 
@@ -30,7 +30,7 @@ Install the gem and npm package:
 
 ```
 gem install yrby-actioncable # depends on yrby
-npm install @yrby/client
+npm install yrby-client
 ```
 
 ## What you get
@@ -41,25 +41,27 @@ npm install @yrby/client
   one-include ActionCable concern.
 - Authoritative record-before-distribute semantics: each document change can be
   recorded durably before it goes out to anyone.
-- 
+- Optional server-side reads: `Doc#read_text` and `Doc#read_map` reconstruct a
+  document's contents in Ruby - no Node process - for search, exports, validation,
+  or server-side rendering.
 
-## Why "lite"
+## Scope
 
-The "lite" is the size of the surface. `yrby` binds just the part of `y-crdt` you
-need to *sync and persist* collaborative documents - a `Doc`, awareness, and the
-y-websocket protocol primitives. The Ruby side treats a document as opaque CRDT
-state: it applies updates, answers sync handshakes, and records deltas, but never
-reaches in to read or edit the contents. The browser editor owns the document's
-shape.
+`yrby` binds just the part of `y-crdt` you need to *sync and persist* collaborative
+documents - a `Doc`, awareness, and the y-websocket protocol primitives. By default
+the Ruby side treats a document as opaque CRDT state: it applies updates, answers
+sync handshakes, and records deltas without reaching into the contents - the browser
+editor owns the document's shape. When you do need to look inside, `Doc#read_text`
+and `Doc#read_map` reconstruct it server-side, in Ruby.
 
-## What isn't "lite"
+## Durability and delivery
 
-The surface area may be "lite", but a core focus is on durability, resiliency, delivery
+The surface is intentionally small, but the focus is durability, resiliency, delivery
 guarantees, correctness, and thread safety.
 
-Towards that goal, `yrby` adds capabilities that may even stand out in the Yjs ecosystem:
+Towards that goal, `yrby` adds capabilities that stand out even in the Yjs ecosystem:
 
-- Built-in update acknowledgement: the `ActionCableProvider` in `@yrby/client` will continue to
+- Built-in update acknowledgement: the `ActionCableProvider` in `yrby-client` will continue to
   send updates until an ack is received from the server. [`yrby-actioncable`](https://rubygems.org/gems/yrby-actioncable)
   only sends an ack when applying an update is successful. The goal is at-least-once delivery,
   and because CRDTs are idempotent a duplicate update is effectively a no-op.
@@ -197,7 +199,7 @@ for the same document as long as they share the same store and cable adapter.
 
 `on_load` and `on_change` are required. If either is missing, the channel fails 
 before it can acknowledge or broadcast edits. Presence is ephemeral:
-awareness frames are relayed, and `@yrby/client` sends a best-effort
+awareness frames are relayed, and `yrby-client` sends a best-effort
 presence-removal frame on disconnect/pagehide, with the client-side awareness
 timeout as the fallback for abrupt disconnects.
 
@@ -315,7 +317,7 @@ client -> server   { "update": "<base64 update>", "id": 42 }
 server -> client   { "ack": 42 }     # update accepted; safe to forget
 ```
 
-`@yrby/client`'s `ActionCableProvider` handles this automatically. It keeps
+`yrby-client`'s `ActionCableProvider` handles this automatically. It keeps
 the unacknowledged local document tail in a queue and sends the merged tail as a
 single causally-complete delta. The id is the highest sequence in the batch, so
 one `{ ack: id }` cumulatively confirms everything up to it. Because CRDT apply
@@ -324,7 +326,7 @@ re-acks. Awareness stays ephemeral and is not acked.
 
 Presence (cursors, selections) is owned by the browser clients — the server
 never sets or holds presence state, it only relays awareness frames opaquely.
-See `@yrby/client` for the client-side awareness API.
+See `yrby-client` for the client-side awareness API.
 
 ## Thread Safety
 

data/lib/y/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Y
-  VERSION = "0.2.0"
+  VERSION = "0.2.3"
 end

data/lib/y.rb

@@ -3,13 +3,13 @@
 require_relative "y/version"
 
 # Load the native extension. Precompiled gems ship it in a per-Ruby-version
-# subdir (lib/y/<major.minor>/y_ruby.<ext>); a source build puts it flat at
-# lib/y/y_ruby.<ext>. Try the versioned path first, fall back.
+# subdir (lib/y/<major.minor>/yrby.<ext>); a source build puts it flat at
+# lib/y/yrby.<ext>. Try the versioned path first, fall back.
 begin
   RUBY_VERSION =~ /(\d+\.\d+)/
-  require_relative "y/#{Regexp.last_match(1)}/y_ruby"
+  require_relative "y/#{Regexp.last_match(1)}/yrby"
 rescue LoadError
-  require_relative "y/y_ruby"
+  require_relative "y/yrby"
 end
 
 module Y

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: yrby
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.3
 platform: aarch64-linux
 authors:
 - JP Camara
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2026-06-29 00:00:00.000000000 Z
+date: 2026-07-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: minitest
@@ -66,8 +66,8 @@ files:
 - LICENSE
 - README.md
 - lib/y.rb
-- lib/y/3.4/y_ruby.so
-- lib/y/4.0/y_ruby.so
+- lib/y/3.4/yrby.so
+- lib/y/4.0/yrby.so
 - lib/y/decoder.rb
 - lib/y/decoder/version.rb
 - lib/y/version.rb