custom {imagesoutdir} not always respected, as it's hardcoded in text2confl

[feliksik]

If I modify {imagesoutdir}, it's not always respected because it's re-configured to the workDir

There are some various scenario's (set it in text2confl.yaml, set it in the .adoc file, setting the document attribute in an extension) that behave slightly differently. I'm not detailing this all now, but I'll just put this as a mental note and refer to this minor bug in my work.

Maybe the config.attributes should be appended after parameters.extraAttrs here, but i'm not sure what side-effects that would have, as other pieces of code may make some assumptions i'm not aware of.

Feel free to keep this open or close as you see fit, given your product goals.

[zeldigas]

@feliksik this is indeed a problem, as imagesoutdir can be changed. Do you have some real world example when this is done in your case, how it breaks upload (I suppose files are not found or smth like this) and any ideas how do you want to it work?

[feliksik]

My usecase is that I don't want to see the generated images; it now pollutes my workspace, and I wanted to hide them in some /tmp or .hidden directory. Now I run a rm -f diag-plantuml-md5-*.png in a script afterwards -- which also works.

So not urgent for me :-)