Why require a saga state?

[izzycoding]

If I am reading the intent correctly then the state hardly ever requires more than the I’d and correlation id.

so I wonder if it would be useful to provide a general saga state class such that the saga doesn’t require the manual registration of different state types explicitly?

public class Saga<T> could internally create a public record SimpleSagaState<T>(...) where “T” is the saga class defined by the user.
Also the saga registration at startup would no longer need the be explicit about registering a state type.

Or is the state able to store other data too?

[mizrael]

the Saga state can be used to store additional data. Thanks for pointing this out, I'll add another sample showing this.
I also like the idea of the SimpleSaga class, exposing just the id and correlation id. Would make the code way easier.