Currently, all parameters to filenames in commands/recipes are resolved to their absolute path.
However, this currently leads to inconsistent resolving situations, and way too complicated code.
It'd be easier, if the "context" of any command to-be-run (by TaskExec) should run in the context of the current working directory being the (sub)folder of the Item, that command is configured in.
For example, what shall be possible:
- MediaConch Recipe in Item subfolder [TIFF].
mediaconch --OutputJSON=../report.json *.tif: should run in ./TIFF/ and create a file called "TIFF/../report.json" - so one level up.
Anyways: Make sure the parser for recipe placeholders works consistently and as expected.
Currently, all parameters to filenames in commands/recipes are resolved to their absolute path.
However, this currently leads to inconsistent resolving situations, and way too complicated code.
It'd be easier, if the "context" of any command to-be-run (by TaskExec) should run in the context of the current working directory being the (sub)folder of the Item, that command is configured in.
For example, what shall be possible:
mediaconch --OutputJSON=../report.json *.tif: should run in ./TIFF/ and create a file called "TIFF/../report.json" - so one level up.Anyways: Make sure the parser for recipe placeholders works consistently and as expected.