Feat/master/autogeneration

[ognjenkatic]

This PR is a major refactor of the client project. It switches over from hand written client code to semi auto generated (NSwag) to achieve full support for conductor API and make it easier to follow changes. There is a layer of abstraction in between the caller and the auto generated code that makes the method names a bit more meaningful.

We also took the opportunity to move to .Net6 and do some code changes to take advantage of some of the newer language features.

[boma96]

Some comments to consider

[boma96]

@ognjenkatic Also can you put nswag file used to generate models and client into repository

[ognjenkatic]

@ognjenkatic Also can you put nswag file used to generate models and client into repository

This would be two files, as we split it into models and client file. Lets see if we like what we made and do some testing. If it works out, I will add them to the .sourcegen directory.

[boma96]

We should test this parallel scenario before making stable release. In following days I plan to introduce some changes so after that we can do proper release

[boma96]

@ognjenkatic I just noticed that you used WorkflowTaskType instead of Type in Builders.
According to docs type should be used. Also swagger file contains both type and workflowTaskType for some reason.

[ognjenkatic]

@ognjenkatic I just noticed that you used WorkflowTaskType instead of Type in Builders. According to docs type should be used. Also swagger file contains both type and workflowTaskType for some reason.

Conductor seems to allow setting workflow task type in two ways, either as a string type or enum workflowTaskType.

In the generated models setWorkflowTaskType is a non nullable enum, so if not set to actual task type explicitly on our end it will have the first enum value SIMPLE.

[ognjenkatic]

Both string and enum values are now sent for type.