Changed #

• BREAKING: RaiserEvent is now a pure abstract interface class instead of a base class with implementation
  • Note: Using RaiserEvent is completely optional - EventBus works with ANY type
  • If you choose to use RaiserEvent, you must explicitly implement all three required properties: id, occurredOn, and metadata
  • No more automatic property initialization - implement the interface explicitly
  • This change allows events to use composition and multiple interfaces without inheritance constraints
• RaiserEvent now implements ZooperDomainEvent from zooper_flutter_core package
  • Added zooper_flutter_core: ^1.0.2 as an optional dependency (only needed if you use RaiserEvent)
  • Ensures consistency across domain events in the Zooper ecosystem
• Event IDs in RaiserEvent now use EventId type (ULID-based) instead of String
  • IDs are generated via EventId.fromUlid() for better uniqueness guarantees
  • Access raw string value via event.id.value when needed
• Renamed RaiserEvent.timestamp property to occurredOn for clarity and DDD alignment
• Removed aggregateId as a direct property from RaiserEvent
  • Store aggregate identifiers in the metadata map instead: metadata: {'aggregateId': 'user-123'}
  • Access via event.metadata['aggregateId'] as String?
• Removed all helper mixins and convenience extensions
  • No more StandardRaiserEvent mixin
  • No more extension methods for aggregateId or timestamp accessors
  • Events implementing RaiserEvent must be implemented explicitly following the interface pattern

Important Note #

EventBus is fully generic and does not require RaiserEvent! You can publish and subscribe to any type. The RaiserEvent interface is purely optional for users who want standardized domain event metadata.

Changed #

• Migrated generator implementation away from deprecated analyzer element APIs to remove deprecation warnings.

Changed #

• BREAKING: Renamed DomainEvent to RaiserEvent to avoid naming conflicts with other packages

Added #

• EventBus — Central dispatcher for publishing and routing domain events
• DomainEvent — Base class with automatic ID generation, timestamps, and optional aggregate ID
• EventHandler — Type-safe interface for class-based event handlers
• Subscription — Handle for cancelling handler registrations
• Priority-based ordering — Higher priority handlers execute first
• Error handling strategies
  • ErrorStrategy.stop — Halt on first error (default)
  • ErrorStrategy.continueOnError — Collect errors, throw AggregateException
  • ErrorStrategy.swallow — Silent failures with optional callback
• AggregateException — Collects multiple handler errors when using continueOnError
• Comprehensive examples demonstrating basic and advanced usage patterns