Assigning an enum to an input causes a workflow error (DSL)

[cenini]

Describe the bug
A clear and concise description of what the bug is.

Assigning an enum to a step input causes a workflow error even when the assigned data is of the same type, and should be directly assignable. The below JSON caused this issue

{ "Id": "SomeStep", "StepType": "SomeStepTypeWithEnumInput, SomeNamespace", "Inputs": { "MyEnum": "data[\"MyEnumKeyInIndexableData\"]" }, },

The step has a property like

public class SomeStepTypeWithEnumInput : StepBodyAsync { public MyEnum MyEnum { get; set; } ... }

To Reproduce
Load a workflow definition containing a similar step as above with the DefinitionLoader. The step cannot be run, as the input cannot be assigned to the property.

Expected behavior
The input is assigned to the property, and the step executes.

Additional context
The problem has to do with the DSL. I'll put up a pull request for fixing this issue shortly.

[LambertW]

@danielgerlag could you review and merge this request for support enum type convertible in yaml file?