When passing a single file for a converter that supports multiple files as input, the library throws an exception:
Therefore, we cannot use it in dynamic environments, like running user workflows. If the user adds an IMAGES to PDF endpoint, we cannot force him to strictly pass multiple files to run this workflow. Whether he passes a single image or multiple images, we must return to him a PDF. REST-API supports this, so the library should not throw an exception.
For example, a workflow like this:
- DOCX to PNG
- IMAGES to PDF
Would fail if the initial DOCX file contains a single page, and the first conversion results in a single image.
When passing a single file for a converter that supports multiple files as input, the library throws an exception:
Therefore, we cannot use it in dynamic environments, like running user workflows. If the user adds an
IMAGES to PDFendpoint, we cannot force him to strictly pass multiple files to run this workflow. Whether he passes a single image or multiple images, we must return to him a PDF. REST-API supports this, so the library should not throw an exception.For example, a workflow like this:
Would fail if the initial DOCX file contains a single page, and the first conversion results in a single image.