v2.0.0

[idugalic]

• Major update of the library
  • Non-compatible changes on the application layer components.
  • Repository interfaces, Aggregate interfaces, and Materialized view interfaces are simplified / many interfaces are replaced by one interface.
  • Repository interfaces, aggregate interfaces, and Materialized view interfaces include metadata of the message (command metadata, event metadata, ...)
  • Metadata types exist only on the application layer, not leaking into the domain, as these don't benefit core logic. Example: traceId, correlationId, ...

Metadata is combined with payload types using Intersection Types in Typescript.

Intersections provide more flexibility and can handle more complex scenarios:

• Flexibility: If you anticipate needing to access individual components of the combined state separately, using tuples might be more appropriate, as it allows you to maintain separate types for each component. However, if you primarily need to treat the combined state as a single entity with all properties accessible at once, intersections might be more suitable.

• Readability: It better communicates your intentions and the structure of your data.

TypeScript adopts a structural type system which determines type compatibility and equivalence based on the type structure or definition rather than the declarative relationship between types and interfaces, which contrasts with nominal type system.

Besides keeping the focus on separating data from behavior, we want to split the responsibilities between the domain and application/adapter layers better, steering your design in a good direction.