It is extremely complicated to implement dynamic converters using the C# library. It is impossible to integrate a dynamic form/workflow, etc., without writing a ton of extra code and extra dependencies to parse the OpenAPI schema manually.
I suggest implementing a strongly typed model for the converter, something like:
publicclassConverter{publicstringTitle{get;set;}publicstringSummary{get;set;}publicstringAcceptsFormats{get;set;}// to build a form with accepts=".docx,.dot.,.doc" attributepublicboolAcceptsMultiple{get;set;}publicDictionary<string,string>Parameters{get;set;}
...}And a method GetConverterInfo(src, dst), that parses the OpenAPI schema under the hood and returns a strongly typed model with all the required metadata about the converter, which allows building dynamic converters effortlessly.
It is extremely complicated to implement dynamic converters using the C# library. It is impossible to integrate a dynamic form/workflow, etc., without writing a ton of extra code and extra dependencies to parse the OpenAPI schema manually.
I suggest implementing a strongly typed model for the converter, something like:
And a method
GetConverterInfo(src, dst), that parses the OpenAPI schema under the hood and returns a strongly typed model with all the required metadata about the converter, which allows building dynamic converters effortlessly.