exportOutDirName relative to source file location

Loving the extension, but one thing that I still can’t get right is how to properly set the output directory, even looking at #82 and such.

What I’m looking for:

a/
    b/
        diagrams/
            source/
                mydiagram.puml
            out/
                My Diagram.png

If I just set exportOutDirName to…

• out, I get out/a/b/diagrams/source/My Diagram.png
• ./out, I get out/a/b/diagrams/source/My Diagram.png
• ., I get a/b/diagrams/source/My Diagram.png
• a/b/diagrams/out, I get a/b/diagrams/out/a/b/diagrams/source

Is there an existing way to do what I want? exportOutDirName sets the root of output path, but even with exportSubFolder as false, all directories are still copied (just no separate directory based on the diagram source file name). Maybe an extra option is needed to control the behavior about how directories are copied?

[qjebbs]

@larslue, About your proposal, consider dir structure like this:

diagrams/
    source/
        dir1/
            mydiagram.puml
        dir2/
            mydiagram2.puml

It would be:

diagrams/
    source/
        mydiagram.png
        mydiagram2.png
        dir1/
            mydiagram.puml
        dir2/
            mydiagram2.puml

To your case, try:

exportOutDirName: "."
exportSubFolder: false

[chipbite]

What I find counter-intuitive is the fact that using exportOutDirName: "." will actually set the path to relative to the input file, but using a relative path like exportOutDirName: "./out/" will act as the default and create an export path that is relative to the workspace root.

This is a good and valid observation, I think. (I don’t have a solution proposal though.)