You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we create all types (data classes, value classes, enums and exceptions) contained in a protocol declaration in a single file (protocol-types.kt).
For better readability and to prepare separation of concerns for command- and query side, it would be nice to have multiple files (*-events.kt, *-commands.kt, *-queries.kt, ...).
This can be done by using a fileSpecList strategy and splitting the different types using the meta properties.
The text was updated successfully, but these errors were encountered:
Currently we create all types (data classes, value classes, enums and exceptions) contained in a protocol declaration in a single file (
protocol-types.kt
).For better readability and to prepare separation of concerns for command- and query side, it would be nice to have multiple files (
*-events.kt
,*-commands.kt
,*-queries.kt
, ...).This can be done by using a fileSpecList strategy and splitting the different types using the meta properties.
The text was updated successfully, but these errors were encountered: