Class ConfigViolation

ConfigViolation indicates system configuration or routing issues where events are mismatched with their handlers. This occurs separately from contract violations and represents problems with the system topology itself, such as:

  • Events sent to handlers not configured to process them
  • Mismatched event types not covered by handler contracts
  • Configuration conflicts between services

Requires explicit resolution as it indicates fundamental routing or setup issues.

Hierarchy

  • ViolationError<"Config">
    • ConfigViolation

Constructors

constructor

Properties

message metadata name stack? type prepareStackTrace? stackTraceLimit

Methods

captureStackTrace

Constructors

constructor

Properties

message

message: string

Readonlymetadata

metadata: null | Record<string, any>

Additional structured data about the violation

Readonlyname

name

The error name, formatted as ViolationError This helps with error identification in logs and stack traces

Optionalstack

stack?: string

Readonlytype

type

The specific type/category of the violation

Static OptionalprepareStackTrace

prepareStackTrace?: ((err: Error, stackTraces: CallSite[]) => any)

Optional override for formatting stack traces

See

https://v8.dev/docs/stack-trace-api#customizing-stack-traces

StaticstackTraceLimit

stackTraceLimit: number

Methods

StaticcaptureStackTrace

  • captureStackTrace(targetObject, constructorOpt?): void

  • Create .stack property on a target object

    Parameters

    • targetObject: object
    • OptionalconstructorOpt: Function

    Returns void

Settings

Member Visibility

On This Page

Constructors
Properties
Methods