When starting the stream we are required to tie it to a certain type. Would be nice to be able to pass in a custom string and there by classifying (naming) the stream and not tie it to a certain concrete type/model.
Or is it really used for anything internally? On the way out, I get that a type could be needed, when e.g. consuming a stream with snapshots, but then I will be needed to specify a target type anyway, no?
That would allow us to use the stream state for versioning, meta etc. and consume the related events as pure events to a stream and not care about models.
Alternatively, not require a certain type being stored and the be able to pass custom meta that can be attached to the stream and acquired via FetchStreamState
danielwertheim
commented
7 years ago
When starting the stream we are required to tie it to a certain type. Would be nice to be able to pass in a custom string and there by classifying (naming) the stream and not tie it to a certain concrete type/model.
Or is it really used for anything internally? On the way out, I get that a type could be needed, when e.g. consuming a stream with snapshots, but then I will be needed to specify a target type anyway, no?
That would allow us to use the stream state for versioning, meta etc. and consume the related events as pure events to a stream and not care about models.
Alternatively, not require a certain type being stored and the be able to pass custom meta that can be attached to the stream and acquired via
FetchStreamState