Skip to content

feat: a package can list the events it dispatches without constructing its emitters - #29

Merged
rodrigoteamx merged 1 commit into
mainfrom
feat/a-package-declares-its-events-in-its-manifest
Sep 8, 2026
Merged

rodrigoteamx merged 1 commit into
mainfrom
feat/a-package-declares-its-events-in-its-manifest

Conversation

@rodrigoteamx

Copy link
Copy Markdown
Contributor

Greenhouse decisions/0228, second slice. Measured on cattle (evidence 0567): with every emitter declaring at construction, events:catalogue in a CLI process listed 7 of the family's 24 framework events — the rest belong to emitters that process never builds. Milpa\Interfaces\Event\DeclaresEvents is the holder contract (static declarations(): list<EventDeclaration>), readable from a class name a package manifest names, so a host can declare on behalf of an emitter nobody constructed. Additive: nothing existing implements it yet.

…g its emitters

An emitter declares to the dispatcher when it is built, so a process that never builds it never hears about its events: measured on fresh cattle, a CLI process knew seven of the family's twenty-four (greenhouse decisions/0228). DeclaresEvents is the holder contract that answers one step earlier — a static list of EventDeclaration a host can read from a class name found in a package manifest, and declare on behalf of an emitter this process will never construct.
@rodrigoteamx
rodrigoteamx merged commit d9e09b4 into main Sep 8, 2026
2 checks passed
@rodrigoteamx
rodrigoteamx deleted the feat/a-package-declares-its-events-in-its-manifest branch September 8, 2026 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant