event_engine 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: dec18ac1cb2f4605efaec53cc844453046e5ee7d9e1c111bb7a303ac8e10eb03
-  data.tar.gz: a1e46a6755d4f04675ee8a7931dc226f6d386de00bf5c69aea2cc644b3c68bd7
+  metadata.gz: 9f780a13e96d7a1fd1534d39aeda5cca32379d283e886839538f969d2cdcfa53
+  data.tar.gz: 1dad812c37e3d4b44178d8d2a9b42b1623a94fef984c6e32d66f84a0b4a3d76a
 SHA512:
-  metadata.gz: 5ecdfe7997ff911c9ee0cb24b55ebdf3a749b9f3a038884e320eeddfb4c3bb10ee8b405b03593c51c4709bb3a151640cdfdb3c541e9cbd975f40b9e023058b00
-  data.tar.gz: fba7d789ab7a5dbefb02dbcc368bee0379f7131552413b33914bc8a1391af7e33c9080e98f307d391acb1d5f17119e855b2d497cbbfed2f7c0704a85a031056e
+  metadata.gz: 685bad2445b1b6022625790855b51c4614be06e7cfafc81556d959a1a2d3254663a5a701bccfdc805c3260ec19919e939f22a5733d64481bdf894a60daeae896
+  data.tar.gz: bd15af2c996f15d0422b624947c78fa2d2607e13a611b028ed6f03a3d5a470ee3d8963c15c038976c5bb2c164f3eebe41a90fe372d4c3c28b39abb0e4fa8d955

data/CHANGELOG.md

@@ -7,6 +7,24 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.2.1] - 2026-07-29
+
+### Fixed
+
+- Running `event_engine:catalog` broke `emit`. The task scaffolds a rules file
+  listing every catalogued event with no value, and those bare keys counted as
+  declared rules — so routing was considered active while every event resolved to
+  nothing, raising `UnroutableEventError` on emit until each rule was filled in.
+
+  An app that processes events through **handlers** rather than processors — for
+  example one using `event_engine-store`, whose `Recorder` observes every event —
+  could not emit at all after building its catalog.
+
+  An undecided rule is now treated as no rule: a rules file where nothing is decided
+  behaves exactly like no rules file, and `event_engine:rules:check` still reports
+  the undecided events so the gap stays visible.
+
+
 ## [0.2.0] - 2026-07-29
 
 This release completes the split between **authoring** and **runtime**. Events are

data/README.md

@@ -82,6 +82,15 @@ What a host still decides for itself is **how** each event is processed, in the
 
 ---
 
+## A working example
+
+[**DYB-Development/event_engine_example**](https://github.com/DYB-Development/event_engine_example)
+is a minimal Rails app wired to this pipeline end to end — declaring an event,
+compiling it, declaring how it is processed, and handling it. It installs all three
+gems from RubyGems, so it is what a real host looks like.
+
+---
+
 ## Getting started
 
 ```ruby

data/lib/event_engine/processing_rules.rb

@@ -29,7 +29,7 @@ module EventEngine
     end
 
     def any?
-      !@default.nil? || @packs.any? || @events.any?
+      processor_names.any?
     end
 
     def processor_names

data/lib/event_engine/version.rb

@@ -1,3 +1,3 @@
 module EventEngine
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: event_engine
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - tylercschneider
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-07-29 00:00:00.000000000 Z
+date: 2026-09-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: railties