Input / Output #245
Input / Output #245
Conversation
|
This is quite nice! We can now avoid all the reflection for workflows that are defined in code, maybe it brings even some performance improvements for fast running workflowsteps. I wanted to do something very similar when I looked at the problem first, but did not want to introduce breaking changes to the Api. |
Co-Authored-By: danielgerlag <daniel@gerlag.ca>
|
Another question... How does it play with the json format of the workflow ? Indeed you could potentially use whatever C# code so can you just put this C# code in the JSON or are there some limitations ? |
|
Actually, the expressions in JSON are not C#... they are parsed with this expression library. https://github.com/StefH/System.Linq.Dynamic.Core/wiki/Dynamic-Expressions#expression-language However, the action based inputs/outputs are not yet available via JSON, I'm still trying to decide the best way to represent this in JSON |
|
I really like the work you did in the documentation of WFC. The samples with the README are really handy and provide information in a quick way. However, the JSON part of WFC is pretty undocumented. Indeed, apart from the small part in the main README file, there is nothing. It would be interesting to provide, in each README file where you showed a specific feature of WFC, the JSON representation of the code used in the sample (or at least some kind of pointer to the format to use for the specific feature). Keep up the good work ;-) |
@dr-BEat @Kahbazi @ssougnez @w-bonelli
Action Inputs / Outputs
Added the action Input & Output overloads on the fluent step builder.
This will allow one to manipulate properties on the step before it executes and properties on the data object after it executes, for example
Breaking changes
The existing ability to assign values to entries in dictionaries or dynamic objects on
.Outputwas problematic, since it broke the ability to pass collections on the Output mappings.This feature has been removed, and it is advised to use the action Output API instead, for example
This functionality remains intact for JSON defined workflows.