Conversation
…#16) Aggregat-CommandHandler sammeln ihr Event (addEvent($event, EventScope::Internal)) und dispatchen NICHT mehr eager; die Publikation nach erfolgreichem Commit ist Sache des Aufrufers / einer Process-Node. Sync auf das neue Modell: - platform-implementation §7: addEvent collects-only + EventScope + getEvents(?EventScope) - rules-testing §C: Event-Emission-Test auf $response->getEvents(EventScope::Internal) statt EventCollector am Dispatcher (Handler dispatcht nicht mehr) - platform-usage: getEvents collected; Publikation post-Commit durch Aufrufer/Process-Node - platform-cookbook §1: Klarstellung Handler collects only EventRouter + eventDispatcher()-Override bleiben unveraendert (E2, dev-owned Transport). Bezug: builder docs/prd/PRD_aggregate_event_publication.md (E1).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v1.0.5 — Doku-Sync der Event-relevanten Skills auf das Aggregat-Event-Publikations-Modell (Phase A). Siehe PR #16.