[BREAKING] refactor: Fix unintuitive binding of StreamAsync (#1930)

In #1551 we added a mechanism to open a Streaming workflow run without providing any input. This caused unintuitive behaviour when passing a string as input without providing a runId, resulting in the input being misinterpreted as the runId and the workflow not executing.

As well, the name caused confusion about why the Workflow was not running when using the input-less StreamAsync (since the Workflow cannot run without any messages to drive its execution).
This commit is contained in:
Jacob Alber
2025-11-05 12:26:46 -05:00
committed by GitHub
Unverified
parent 14aee7e334
commit b8a55dccb4
3 changed files with 7 additions and 6 deletions
@@ -37,7 +37,7 @@ public sealed class InProcessExecutionEnvironment : IWorkflowExecutionEnvironmen
}
/// <inheritdoc/>
public async ValueTask<StreamingRun> StreamAsync(
public async ValueTask<StreamingRun> OpenStreamAsync(
Workflow workflow,
string? runId = null,
CancellationToken cancellationToken = default)