event_engine 0.2.3 → 0.2.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: e487942b070a87cfa23e72a27d34e9247704caadfa887be26c1cd63eb3d4506d
-  data.tar.gz: 4f87ddcd5d44b28009ad2e45bc46296ab52d9f047037ec7023067238554f6a4e
+  metadata.gz: d41f3bf5979d9b7bf564192af007e2345acb7cb5a8557af84a56a9a140ba7b49
+  data.tar.gz: c295ec1cc5a9ad2f1d3f2dec987067e7fbfe33dbf2a6037914989acc5caad9fc
 SHA512:
-  metadata.gz: 6f63838b3a3c2835e9c1511172413f6991cb0831afdf3b21247e5ef5ba03f0d40a92fb21ba1282ef6ce100a5081837821999de9b51f3cc920a2a5b30a94ec9fa
-  data.tar.gz: 688da6973e692d3b57b6d468191c37e9f701fa767888c030aec9318a0193685388ba6441b88be08d5fb54ff85ee6f8f019eee4a91791259ee4cce2af4a3baef2
+  metadata.gz: 0ac2e2d99a33c2a69dd1300d00c53f283504eecba38f79d4ca7b87f4ae8098a689abc9a3588f45e992c31f2141e0c3bf454c21eda0a5bb101bbdbcaa8c813df2
+  data.tar.gz: 0bb6f4f3f401336adfd11076a3df889ea11ddbc5d913125a69af65b40dd04a95c9163f11fe6d20356c01594bccbce7ae943a4d0607c2978aacd7a0770fda62c9

data/CHANGELOG.md

@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.4] - 2026-11-07
+
+### Added
+
+- A rule of `recorded` runs no processor and still passes the event to the handlers registered for every process type in the same call, so an event that is only kept, such as a history a store records, needs no processor or subscriber. It passes `validate_rules!` with no processor registered under that name.
+
 ## [0.2.3] - 2026-10-23
 
 ### Added

data/README.md

@@ -235,6 +235,7 @@ events:
   invoice_voided: audit   # this one event
   lead_converted:         # catalogued but undecided
   lead_scored: unrouted   # defined, not routed yet
+  lead_viewed: recorded   # kept by every-type handlers, processed by nothing
 ```
 
 A rule names a **registered processor**. Resolution is **event → pack → default**,
@@ -259,6 +260,15 @@ passes `validate_rules!` and `event_engine:rules:check`, and emitting it raises
 `EventEngine::UnroutableEventError`. Replace `unrouted` with a processor name once
 the event has one.
 
+### Keeping an event without processing it
+
+Give an event the rule `recorded` when nothing should process it but it should still
+reach the handlers registered for every process type, such as a store that keeps
+each event. No processor runs and none needs to be registered under that name, and
+emitting it passes the event to those handlers in the same call, so an error a
+handler raises reaches the code that emitted it. The event's `process_type` is
+`recorded`.
+
 ### When a rule is wrong
 
 Both misconfigurations fail loudly and name the fix:

data/lib/event_engine/processing_rules.rb

@@ -3,6 +3,7 @@ require "yaml"
 module EventEngine
   class ProcessingRules
     UNROUTED = :unrouted
+    RECORDED = :recorded
 
     def self.load(path)
       return new unless File.exist?(path.to_s)
@@ -35,7 +36,7 @@ module EventEngine
     end
 
     def processor_names
-      ([ @default ] + @packs.values + @events.values).compact.uniq - [ UNROUTED ]
+      ([ @default ] + @packs.values + @events.values).compact.uniq - [ UNROUTED, RECORDED ]
     end
   end
 end

data/lib/event_engine/version.rb

@@ -1,3 +1,3 @@
 module EventEngine
-  VERSION = "0.2.3"
+  VERSION = "0.2.4"
 end

data/lib/event_engine.rb

@@ -145,6 +145,8 @@ module EventEngine
       return event unless resolver.routes?
 
       name = resolver.resolve(event)
+      return event if name == ProcessingRules::RECORDED
+
       processor = processor_registry.fetch(name) || raise(UnregisteredProcessorError.new(name, event))
 
       processor.call(event)

data/the_local/agents/event_engine-develop.md

@@ -147,6 +147,10 @@ off to that local first and come back.
   Keep steps 3 and 4 in the same initializer so they cannot drift.
 - A rule of `unrouted` defines an event before anything handles it. It passes the
   rules check, and emitting it raises `EventEngine::UnroutableEventError`.
+- A rule of `recorded` runs no processor and still passes the event to every
+  handler registered for all process types, such as a store that keeps each event,
+  in the same call. It needs no processor registered under that name and passes
+  the rules check. Use it for an event that is only kept as a history.
 - A pack helper firing an event that is not in the committed catalog raises
   `EventEngine::DefinitionPublisher::EventNotInCatalogError`. That means the
   catalog is stale — rebuild it in step 2, do not work around it in app code.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: event_engine
 version: !ruby/object:Gem::Version
-  version: 0.2.3
+  version: 0.2.4
 platform: ruby
 authors:
 - tylercschneider