We noticed when specifying inputs for a workflow that is used as activity, that auto-publishing consuming workflows breaks because the input names of the workflow definition can clash with properties of the activity definition. Examples are: customProperties and metadata |
||
|---|---|---|
| .. | ||
| Extensions/ActivityExecutionContextExtensions | ||
| Flowchart | ||
| Models | ||
| ObjectConversion | ||
| Serialization/Converters | ||
| Elsa.Workflows.Core.UnitTests.csproj | ||
| ExpressionExecutionContextExtensionsTests.cs | ||