Dispatching Events

Dispatch through the event definition for the strongest payload inference.

Primary API: event dispatch

import UserRegistered from '../events/user/registered'

await UserRegistered.dispatch({
  userId: 'user_1',
  email: '[email protected]',
})

Facade API: Event.dispatch(...)

import { Event } from '@holo-js/events'
import UserRegistered from '../events/user/registered'

await Event.dispatch(UserRegistered, {
  userId: 'user_1',
  email: '[email protected]',
})

Helper API: dispatchEvent(...)

import { dispatchEvent } from '@holo-js/events'
import UserRegistered from '../events/user/registered'

await dispatchEvent(UserRegistered, {
  userId: 'user_1',
  email: '[email protected]',
})

dispatchEvent(...) is the conflict-free helper name for code that should not call through the event object.

Fluent controls

Dispatch returns a pending builder:

await UserRegistered.dispatch({
  userId: 'user_1',
  email: '[email protected]',
})
  .afterCommit()
  .onConnection('redis')
  .onQueue('emails')
  .delay(30)

Available methods:

• .afterCommit()
• .onConnection(name)
• .onQueue(name)
• .delay(value) where value is seconds (number) or a Date

await the pending value directly. No extra execute call is needed.

Dispatch result

Resolved value includes:

• eventName
• occurredAt
• deferred
• syncListeners
• queuedListeners

Dispatch behavior

• sync listeners run inline in registration order
• queued listeners are enqueued and do not block listener completion on async queue drivers
• if a sync listener throws, dispatch rejects and queued fan-out is not performed for that dispatch

Continue

• Queued Listeners
• Transactions And After Commit