clickwrap 0.3.2 → 0.3.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1ea29dba21d2740876c9708ad687520310951911eab737844b59577fbbe24464
-  data.tar.gz: 01140025f14f2c137ba35a25ab694898d31fdbc719a42a488d63204007b0dc85
+  metadata.gz: 4e284e0a7a0474b4dc4d3031424074d45c06dfb3f4432d78a3c64c2ec9ca77ba
+  data.tar.gz: 1b09f1436d6f8b18bcfb7f39b4f4f33e311438bb79a020a6b9f47c777cdada15
 SHA512:
-  metadata.gz: 752ed3dda0897564843222843c444a9c5c945493152ec04e697241871afda8df0eeea9635b3f07296a392f58c46abe763366daa759f0916cd5bb455f56a04e01
-  data.tar.gz: 71e5c6512a165734f941b7e5483b399e8d46e83a3963e05af5ae2d3e077dbcf4eac0b0e7eddebc9ff61b7a9d3b73c551502fb434388c65c1830e2b75a6e0add1
+  metadata.gz: 1778cebf0236280efaab60e63ec3f6591742e12188c27c152923d6ee58ad1eb04bc71c74b14f1b606ed93ea3212d8f307fc31e284db0a595235f20848311907e
+  data.tar.gz: 653515517233ee6b0d94245098c0d5dff6bd48cf3c708183b86158c9147a579aeac9ab345d5b52eda9ac7d53fc8f291feedfc2e286291da26a38fe123cf88f0e

data/CHANGELOG.md

@@ -6,6 +6,35 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.3.3] - 2026-08-31
+
+### Fixed — the actor class survives a reload
+
+- **`config.actor_class` followed the constant it had cached, not the one the
+  app has.** In a Rails app with reloading, every capture after the first code
+  change of a session raised
+
+  ```
+  Clickwrap was asked to record User as the actor, but
+  `config.actor_class_name` says the records that can act are User.
+  ```
+
+  Both halves name the same class, which reads as a contradiction and sends
+  whoever hits it to an initializer that is correct. They were two different
+  Ruby objects printing the same name: `actor_class` memoized the
+  constantized `Class` and re-resolved only when the class NAME changed —
+  which never happens, since the name is set once in an initializer — while
+  Zeitwerk replaces the class behind that name on every edit. The cache then
+  held a class no living record was an instance of, so
+  `actor.is_a?(config.actor_class)` was false for an ordinary `User` and
+  capture refused to record it.
+
+  The memo is gone. `constantize` after the first load is a `const_get` and
+  this is called once per capture rather than in a loop, so it was never
+  buying anything; `parent_controller_class` has always resolved this way.
+  Production was never affected — classes are not reloaded there — but every
+  development session was, from its second edit onwards.
+
 ## [0.3.2] - 2026-08-20
 
 ### Fixed — two guards that looked like they held

data/lib/clickwrap/configuration.rb

@@ -307,16 +307,29 @@ module Clickwrap
       @describe_authentication_with = ensure_callable(value, "describe_authentication_with")
     end
 
-    # The constantized actor class, resolved lazily on first use. Lazy on
-    # purpose: the initializer that sets `config.actor_class_name = "User"` runs
-    # before the User model is necessarily loaded.
+    # The constantized actor class, resolved lazily on EVERY use. Lazy on
+    # purpose: the initializer that sets `config.actor_class_name = "User"`
+    # runs before the User model is necessarily loaded.
+    #
+    # Not memoized, deliberately. This used to cache the resolved Class object
+    # and re-resolve only when the class NAME changed — which is never, since
+    # the name is set once in an initializer. In a Rails app with reloading,
+    # the class behind that name is replaced on every code change: Zeitwerk
+    # unloads the old User and defines a new one, same name, different object.
+    # The cache then held a class no living record was an instance of, and
+    # `actor.is_a?(config.actor_class)` failed for a perfectly ordinary User.
+    #
+    # What that looked like from the outside was worse than the bug: the
+    # ConfigurationError names the offending class and the configured class,
+    # and both printed "User". The message read as a contradiction, sent
+    # people to an initializer that was correct, and came back after every
+    # edit — the first signup of a dev session worked and the second did not.
+    #
+    # `constantize` after the first load is a const_get, and this is called
+    # once per capture rather than in a loop, so there was nothing to save.
+    # `parent_controller_class` below has always resolved this way.
     def actor_class
-      name = actor_class_name
-      if @actor_class.nil? || @actor_class_name_at_resolution != name
-        @actor_class = name.constantize
-        @actor_class_name_at_resolution = name
-      end
-      @actor_class
+      actor_class_name.constantize
     end
 
     def parent_controller_class = parent_controller_class_name.constantize

data/lib/clickwrap/version.rb

@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 module Clickwrap
-  VERSION = "0.3.2"
+  VERSION = "0.3.3"
 
   # The canonical schema version for receipts, event digests, and presentation
   # manifests. This is deliberately independent of VERSION: gem releases may

metadata

@@ -1,13 +1,13 @@
 --- !ruby/object:Gem::Specification
 name: clickwrap
 version: !ruby/object:Gem::Version
-  version: 0.3.2
+  version: 0.3.3
 platform: ruby
 authors:
 - rameerez
 bindir: exe
 cert_chain: []
-date: 2026-08-20 00:00:00.000000000 Z
+date: 2026-08-31 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: actionpack