solid_objects 0.7.2 → 0.7.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3c9697331316791269c98ec881f02a59e7556c2ab2abf98c3feb662e5f8cf742
-  data.tar.gz: 12b0390bfcceca1362e7e1779bcb1562ea2e640259ca9ccefac9835b0b2d9a2e
+  metadata.gz: de78ca94f2c12e3c08d50c7b2512d6dbda67a47571540390c7494c6a828f1d35
+  data.tar.gz: b194c137ff3110cabb6cb2f7319819fdd64f314a9ae2113868438a89acce36b8
 SHA512:
-  metadata.gz: 1acdc877187c455dee2843527e8826a719ab66c2f3917233eb1d565c19b6662a9fd6d319213f3340ada04e60f2d299dff8ad675de8762f65e336630a40b7ef79
-  data.tar.gz: f69a34ac8c724164ec597ad3b78637d8537c1d76a527998aa50fa9f7bd7c3327244449be9555a2214c2a9ae7f019e119b5f35c58ad2d28528ea824aad0a0f538
+  metadata.gz: 78834ecb346469854b6d21d938fe3a6ed2689cd60cb037b22b3ce00025466c172ceb3dacdfcf94f88b0e0739e3dcac1c3e84896c6685bc4fe53d4db565ab8513
+  data.tar.gz: 31fbae44dce542e1fc07fe218bf504eb8627583ecc64895e8d86a5805340aeea47531b5f08a6e844809c31b513998c53c28b90993ae9cd40b864e868323eee27

data/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.7.3 - 2026-08-09
+
+- Coordinate batched component refreshes by revision as well as scope and batch
+  name. Invalidations for one revision arrive as separate WebSocket messages, so
+  the microtask merge could not see them all, and each request aborted the one
+  before it. Only the last component updated. Same-revision requests now run
+  alongside each other and every frame is applied; only a strictly newer
+  revision supersedes an in-flight request. Frames already applied at a revision
+  are not applied twice.
+
 ## 0.7.2 - 2026-08-09
 
 - Render batched component partials as HTML regardless of the request format.

data/app/assets/javascripts/solid_objects/component_batch_refresh.js

@@ -1,5 +1,7 @@
 const pendingBatches = new Map()
 const activeBatches = new Map()
+const appliedRevisions = new Map()
+let requestSequence = 0
 
 class SolidObjectsBatchRefreshElement extends HTMLElement {
   connectedCallback() {
@@ -34,18 +36,26 @@ class SolidObjectsBatchRefreshElement extends HTMLElement {
     pendingBatches.set(key, merged)
     queueMicrotask(() => {
       pendingBatches.delete(key)
-      requestBatch(group, batch, merged.sources)
+      requestBatch(group, batch, revision, merged.sources)
     })
     this.remove()
   }
 }
 
-async function requestBatch(group, batch, sources) {
-  const previous = activeBatches.get(group)
-  previous?.abort()
-
+// Invalidations for one revision arrive in separate WebSocket messages, so the
+// microtask merge cannot see them all. Requests are tracked per revision and a
+// request is only cancelled by a strictly newer one; same-revision requests run
+// alongside each other and every frame is applied.
+async function requestBatch(group, batch, revision, sources) {
+  const parsed = parseRevision(revision)
+  supersedeOlderRequests(group, parsed)
+
+  // Same-revision requests run concurrently, so each needs its own entry.
+  // Sharing one key per revision would leave all but the last untracked and
+  // therefore impossible to supersede.
+  const key = `${group}:${revision}:${(requestSequence += 1)}`
   const controller = new AbortController()
-  activeBatches.set(group, controller)
+  activeBatches.set(key, { controller, group, revision: parsed })
 
   try {
     const url = mergedUrl(sources)
@@ -68,10 +78,29 @@ async function requestBatch(group, batch, sources) {
   } catch (error) {
     if (error.name !== "AbortError") dispatchBatchError(batch, "request_failed")
   } finally {
-    if (activeBatches.get(group) === controller) activeBatches.delete(group)
+    if (activeBatches.get(key)?.controller === controller) activeBatches.delete(key)
   }
 }
 
+function supersedeOlderRequests(group, revision) {
+  if (!revision) return
+
+  activeBatches.forEach((entry, key) => {
+    if (entry.group !== group) return
+    if (!olderRevision(entry.revision, revision)) return
+
+    entry.controller.abort()
+    activeBatches.delete(key)
+  })
+}
+
+function olderRevision(candidate, current) {
+  if (!candidate || !current) return false
+
+  return candidate[0] < current[0] ||
+    (candidate[0] === current[0] && candidate[1] < current[1])
+}
+
 // Every notification for one batch and revision carries the same endpoint and
 // differs only by which components changed, so the union of their tokens is the
 // complete set to render.
@@ -93,6 +122,13 @@ function applyFrame(frame) {
   const target = document.getElementById(frame?.target)
   if (!target || !frame.html) return
   if (!newerRevision(frame.revision, target.dataset.solidObjectsRevision)) return
+  // Concurrent same-revision responses can carry the same frame. The target's
+  // own revision only advances once Turbo applies the stream, so what has
+  // already been applied is tracked here as well.
+  const applied = appliedRevisions.get(frame.target)
+  if (applied && !newerRevision(frame.revision, applied)) return
+
+  appliedRevisions.set(frame.target, frame.revision)
 
   const parsed = new DOMParser().parseFromString(frame.html, "text/html")
   const replacement = parsed.getElementById(frame.target)

data/docs/realtime.md

@@ -173,8 +173,11 @@ they are while giving the client a documented contract with per-frame revisions.
 ### What the protocol guarantees
 
 Only components whose dependencies changed are requested; the rest are never
-named in the batch. Duplicate notifications for the same batch and revision merge
-into one request, and a superseded request for the same batch is aborted. Each
+named in the batch. Notifications for the same batch and revision that arrive in
+one task merge into a single request. Notifications that arrive in separate
+WebSocket messages issue their own requests and all of their frames are applied,
+because cancelling a same-revision request would drop the components it carried.
+Only a strictly newer revision supersedes an in-flight request. Each
 frame carries its own revision and cannot overwrite a target that already holds a
 newer one. Authorization is unchanged: every component in the batch passes the
 same `authorize_query` boundary an individual refresh uses, and the batch name is

data/lib/solid_objects/version.rb

@@ -1,5 +1,5 @@
 # rbs_inline: enabled
 
 module SolidObjects
-  VERSION = "0.7.2"
+  VERSION = "0.7.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: solid_objects
 version: !ruby/object:Gem::Version
-  version: 0.7.2
+  version: 0.7.3
 platform: ruby
 authors:
 - Lucas Carlson