Saga handler with cascading message breaks code generation with MultipleHandlerBehavior.Separated #2058
Description
Describe the bug
When a saga handler returns a cascading message and MultipleHandlerBehavior.Separated is enabled, code generation fails.
To Reproduce
See failing test main...scrodde:wolverine:saga-cascading-messagaes-compiler-error
Expected behavior
Cascading messages from saga handlers should work with Separated mode.
Additional context
- Test file: src/Testing/CoreTests/Persistence/Sagas/using_a_saga_with_separated_behavior_mode.cs
- Workaround: Use IMessageContext.PublishAsync() instead of returning the message (see commented code in test)
- related to Saga handler called twice with MultipleHandlerBehavior.Separated #2057 Saga code generation broken with MultipleHandlerBehavior.Separated + [SagaIdentityFrom] #2056
public async Task Handle(ThingUpdated updated, IMessageContext context)
{
Updates++;
Debug.WriteLine(context.Envelope.Destination);
await context.PublishAsync(new AnotherThingHappened(), new()
{
SagaId = Id.ToString()
});
}