standard_ledger 0.5.0 → 0.5.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 89af058a7d94051bc75f8e853d1be397270b52bc5a02020dfdd41484c6cacda5
-  data.tar.gz: 50eef558981621f3561c42095d294f87f09d7ed18e8fc5a5919c0801262f257b
+  metadata.gz: 74163637dfcb14c019f6481391644b45849cad04108b580e5a8de524720ed1ca
+  data.tar.gz: d022e52db16ba6e838c47c9e94ead8fa1f876afb37ffa5f8b3b5390d4877b157
 SHA512:
-  metadata.gz: 16d8c529a99909adb4739feb0ea76e996ebd709c044bc56dd2722bc041f4c17670d2bb383a48072df9a686bc02b1c2a49add8206618ddeb7fb86dd2b45e61c9f
-  data.tar.gz: 5f152b064c69e8da3f7e2767c4b3914da197599ed64ecc8e512be6c34e334af25337f83fd68080c7811a3f4772df647d5799ae635cb0116409286455bd86bf0e
+  metadata.gz: e9b7f1b51851431f1e44c5129dac815517ce064860a83d210d8f94ed8b30e7a90dc393d92af4e702516fcc0a804e613cc7859d582b4ce042d31220970835fb5d
+  data.tar.gz: c11d063fd3e01c8feb06176742df0167ff363c375de4c03d979a7dee52ca21e1388917fd2e1b10e770409b2a703aa5f223f496bc8f2619368b40fa0c323a1cb9

data/CHANGELOG.md

@@ -6,6 +6,26 @@ project adheres to [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.5.1] - 2026-09-24
+
+### Fixed
+- The `post_ledger_entry` RSpec matcher now listens on the channel
+  `StandardLedger::EventEmitter` emits through. It only subscribed to
+  `ActiveSupport::Notifications`, but on Rails 8.1+ the gem emits through
+  `Rails.event.notify`, so the matcher saw no events at all: every positive
+  expectation failed and every `not_to post_ledger_entry` passed without
+  checking anything. When `EventEmitter.rails_event_available?` is true, the
+  matcher now subscribes a collector to `Rails.event` for the block and
+  unsubscribes it afterwards.
+
+### Documentation
+- README **Testing** section (and `AGENTS.md`) said the RSpec support hook
+  calls `StandardLedger.reset!`. It calls `reset_mode_overrides!`, which keeps
+  host initializer configuration intact.
+- The engine initializer comment now tells hosts to subscribe via
+  `Rails.event.subscribe` on Rails 8.1+ rather than
+  `ActiveSupport::Notifications.subscribe`.
+
 ## [0.5.0] - 2026-09-22
 
 ### Changed
@@ -446,7 +466,8 @@ roadmap.
   and `:trigger` (host-owned, gem records rebuild SQL).
 - `standard_ledger:doctor` rake task (verifies trigger presence, etc.).
 
-[Unreleased]: https://github.com/rarebit-one/standard_ledger/compare/v0.5.0...HEAD
+[Unreleased]: https://github.com/rarebit-one/standard_ledger/compare/v0.5.1...HEAD
+[0.5.1]: https://github.com/rarebit-one/standard_ledger/compare/v0.5.0...v0.5.1
 [0.5.0]: https://github.com/rarebit-one/standard_ledger/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/rarebit-one/standard_ledger/compare/v0.3.0...v0.4.0
 [0.3.0]: https://github.com/rarebit-one/standard_ledger/compare/v0.2.0...v0.3.0

data/README.md

@@ -381,12 +381,15 @@ The gem ships an opt-in RSpec support file. Hosts add this to their
 require "standard_ledger/rspec"
 ```
 
-That registers a `before(:each)` hook that calls `StandardLedger.reset!`
-between examples (so per-spec configuration doesn't leak), and exposes:
+That registers a `before(:each)` hook that calls
+`StandardLedger.reset_mode_overrides!` between examples (so `with_modes`
+overrides don't leak). It deliberately does not call the full `reset!`, which
+would wipe configuration your initializers set up. It also exposes:
 
 - `post_ledger_entry(EntryClass).with(...)` — a block matcher that
-  subscribes to the `<namespace>.entry.created` notification for the
-  duration of the block and asserts an entry of the expected class was
+  subscribes to the `<namespace>.entry.created` event for the duration of
+  the block, on the same channel the gem emits through (`Rails.event` on
+  Rails 8.1+, `ActiveSupport::Notifications` otherwise), and asserts an entry of the expected class was
   written (with optional `kind:`/`targets:`/`attrs:` constraints).
 
   ```ruby

data/lib/standard_ledger/engine.rb

@@ -12,8 +12,10 @@ module StandardLedger
 
     initializer "standard_ledger.notifications", after: :load_config_initializers do
       # Notification wiring lands here in a follow-up PR. Today this is a
-      # no-op — the gem emits events but ships no internal subscribers; hosts
-      # subscribe directly via ActiveSupport::Notifications.subscribe.
+      # no-op — the gem emits events but ships no internal subscribers. On
+      # Rails 8.1+ events go through `Rails.event.notify`, so hosts subscribe
+      # with `Rails.event.subscribe`; on older Rails they fall back to
+      # ActiveSupport::Notifications (see StandardLedger::EventEmitter).
     end
 
     # Engines auto-discover `lib/tasks/*.rake` in most Rails versions, but

data/lib/standard_ledger/rspec/matchers.rb

@@ -1,5 +1,28 @@
 require "rspec/expectations"
 require "active_support/notifications"
+require "standard_ledger/event_emitter"
+
+module StandardLedger
+  module RSpec
+    # Collects `<namespace>.entry.created` payloads from `Rails.event` for the
+    # duration of a `post_ledger_entry` block. A dedicated object (not a
+    # Proc) because `EventReporter#unsubscribe` matches with `===`.
+    #
+    # @api private
+    class RailsEventCollector
+      attr_reader :payloads
+
+      def initialize(event_name)
+        @event_name = event_name
+        @payloads = []
+      end
+
+      def emit(event)
+        @payloads << event[:payload] if event[:name] == @event_name
+      end
+    end
+  end
+end
 
 # `post_ledger_entry` — assert that a block of code wrote a ledger entry.
 #
@@ -22,7 +45,9 @@ require "active_support/notifications"
 #   expect { ... }.to_not post_ledger_entry(VoucherRecord)
 #
 # The matcher subscribes to `<namespace>.entry.created` for the duration of
-# the block, captures every fired event, and asserts that at least one event
+# the block, on whichever channel `StandardLedger::EventEmitter` emits through
+# (`Rails.event` on Rails 8.1+, `ActiveSupport::Notifications` otherwise),
+# captures every fired event, and asserts that at least one event
 # matched the expected class (and, when chained, the expected `kind`,
 # `targets`, and `attrs`). The notification namespace is read from
 # `StandardLedger.config.notification_namespace`, so a host that customised
@@ -71,10 +96,35 @@ RSpec::Matchers.define :post_ledger_entry do |entry_class|
   # Helpers
   # ----------------------------------------------------------------------
 
+  # Listens on the same channel `EventEmitter.emit` picks. Listening only on
+  # AS::Notifications meant that on Rails 8.1 (where emit goes through
+  # `Rails.event`) the matcher saw nothing — every positive expectation
+  # failed and every negated one passed vacuously.
   def capture_entry_created_events(&block)
+    if StandardLedger::EventEmitter.rails_event_available?
+      capture_via_rails_event(&block)
+    else
+      capture_via_notifications(&block)
+    end
+  end
+
+  def capture_via_rails_event(&block)
+    bus = ::Rails.event
+    collector = StandardLedger::RSpec::RailsEventCollector.new(notification_event_name)
+    bus.subscribe(collector)
+
+    begin
+      block.call
+    ensure
+      bus.unsubscribe(collector)
+    end
+
+    collector.payloads
+  end
+
+  def capture_via_notifications(&block)
     events = []
-    name = notification_event_name
-    subscriber = ActiveSupport::Notifications.subscribe(name) do |*args|
+    subscriber = ActiveSupport::Notifications.subscribe(notification_event_name) do |*args|
       events << ActiveSupport::Notifications::Event.new(*args).payload
     end
 

data/lib/standard_ledger/version.rb

@@ -1,3 +1,3 @@
 module StandardLedger
-  VERSION = "0.5.0"
+  VERSION = "0.5.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: standard_ledger
 version: !ruby/object:Gem::Version
-  version: 0.5.0
+  version: 0.5.1
 platform: ruby
 authors:
 - Jaryl Sim