recourse 4.7.0 → 4.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ba211bbbb2cad39fb435db7af8c982733056778da14b2617ed01616d7b471643
-  data.tar.gz: 3b847c74cb62a88425a882a839fc6d264581ab3f7e8aed661f53e03b184a12ed
+  metadata.gz: 2de6346d2ca14ff89cc09ff75c23b72b6cc7b7502d9dcfebcb29253a53209c8c
+  data.tar.gz: aadab8161994fb71579e46a1ab1343f929f11fdf7bec5b113768f06c16887bc8
 SHA512:
-  metadata.gz: 7ba31e2730714820fa039e61ba649fc91e3b944b01703ded5c4a006b52068b0b5dc8997f667481994adb4d4fb4370660b3d2eed5fa0bb882d8307a44b0bc82ab
-  data.tar.gz: 99f83b13ef7fb727d140dcb6fbd44a3abb160fd10b2bd21d441fa4cb609e985463b66e044047503acdb69375645c8dc408ab2559d4faa00d62416a8dea95a9a9
+  metadata.gz: 655ce30df22d4cccd72dd6a48e559eba1e8d14720d14f2a032de9f811a510f81f5a99dbf1be8082599371eff60c24906932b682e910099cd6bc72a6dbb12bd29
+  data.tar.gz: cb32000306a3b2f20e27f6898aed2c6d3ffb78bbf32411779f85a6e28bb4c61e80d327fddf2fbca0cf82163d9e0f198997eb0b22cea5f211fc23d2d4f7b30822

data/CHANGELOG.md

@@ -5,6 +5,26 @@ All notable changes to this project will be documented in this file.
 For more information about changelogs, check [Keep a Changelog](http://keepachangelog.com) and
 [Vandamme](http://tech-angels.github.io/vandamme).
 
+## 4.8.0 - 2026-09-13
+
+* [Feature] A table is redrawn when a record its rows draw changes, so a `touch: true` kept for that alone can go
+
+  A cell naming a key draws the record it points at — a booking's row reading its
+  contact's phone — and the relation's own version, `COUNT(*)` and `MAX(updated_at)`
+  over the page, sees only the rows themselves. The table kept the number the contact
+  had when the fragment was written, until somebody wrote to the booking. The key now
+  carries the newest `updated_at` among everything `recourse_includes` names, which
+  the index eager-loads already — so it is read off the records in memory and costs no
+  query.
+
+  A host that declared `belongs_to ..., touch: true` to expire such a table can drop
+  it: a touch is an UPDATE per parent per child write, it contends on the parent row,
+  and it makes every child write look like a parent update to every `after_commit` the
+  parent has. One that says a domain fact — a parent genuinely updated by its child —
+  stays. Where a row of a host's own reads through a second key, name that in
+  `recourse_includes` as a hash, the shape `includes` already takes, and the version
+  follows it there.
+
 ## 4.7.0 - 2026-09-11
 
 * [Feature] The toast after a create or an update names the record and links it to its page

data/app/views/recourses/_table.html.erb

@@ -1,8 +1,11 @@
 <%# locals: (recourses:, pagy:) %>
 <%# A sorted or filtered table is drawn live: two requests can ask for one relation
     and want different headings, since only one of them clicked a heading to get it. -%>
-<%# The key carries three riders. The row partial's digest: a host's `_row` is
-    resolved at render, which the fragment's own template digest never follows.
+<%# The key carries what the rows draw besides their own columns: `MAX(updated_at)`
+    over the relation sees only the rows themselves, so a name or a ZIP read off the
+    record a row points at would keep whatever it said when the fragment was written.
+    And the row partial's digest: a host's `_row` is resolved at render, which the
+    fragment's own template digest never follows.
     And the column list: which columns a table shows is decided in Ruby —
     `recourse_hidden`, timestamps, counters — that no digest covers either. And the
     bookmarks, which are the viewer's rather than the relation's — so this is what
@@ -10,7 +13,8 @@
     the fragment when a square is clicked. And the zone, for the same reason again:
     a timestamp is drawn against the reader's own clock, so without it the first
     person to load a table would settle what hour everybody else read. -%>
-<% key = [recourses, row_digest, resource_columns, bookmark_digest, Time.zone.name] -%>
+<% key = [recourses, rows_version(recourses), row_digest, resource_columns,
+          bookmark_digest, Time.zone.name] -%>
 <% cache_if cacheable_table?, key do %>
   <% actions = resource_actions %>
   <div class='table-responsive'>

data/lib/recourse/helpers/rows.rb

@@ -17,6 +17,36 @@ module Recourse
         ActionView::Digestor.digest name: row.virtual_path, format: :html, finder: lookup_context
       end
 
+      # What the rows draw besides their own columns. A cell naming a `*_id` reads the
+      # record it points at, and `MAX(updated_at)` over the relation only ever sees the
+      # rows themselves -- so without this a table keeps a name, a phone or a ZIP that
+      # the record it belongs to has since changed.
+      #
+      # Read off the objects rather than the database: the index eager-loads exactly
+      # these, so every one of them is already in memory and this costs no query. And
+      # written out to the microsecond, which is what `cache_key_with_version` keeps
+      # too: a key expands a time by `to_s`, and two writes inside one second would
+      # otherwise be one version.
+      def rows_version(rows)
+        drawn = reached rows, resource_model.recourse_includes
+
+        drawn.filter_map { |one| one.try :updated_at }.max&.utc&.to_fs :usec
+      end
+
+      # Every record the rows reach along `includes`, in any shape `includes` accepts:
+      # a name, a list of them, or a hash naming what to follow from there.
+      def reached(rows, names)
+        Array.wrap(names).flat_map do |name|
+          next along rows, name unless name.is_a? Hash
+
+          name.flat_map { |one, nested| followed along(rows, one), nested }
+        end
+      end
+
+      def followed(rows, nested) = rows + reached(rows, nested)
+
+      def along(rows, name) = rows.flat_map { |row| Array.wrap row.public_send(name) }
+
       # Whether the table may be kept at all. A sorted or filtered one never is: two
       # requests can ask for one relation and want different rows, and only one of them
       # clicked a heading to say so.

data/lib/recourse/version.rb

@@ -1,4 +1,4 @@
 module Recourse
   # Version of the gem, read by the gemspec and by hosts checking compatibility.
-  VERSION = '4.7.0'
+  VERSION = '4.8.0'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: recourse
 version: !ruby/object:Gem::Version
-  version: 4.7.0
+  version: 4.8.0
 platform: ruby
 authors:
 - claudiob