kvid

@jaggzh - please reopen this issue and explain why if you don't agree that #212 covers your use case.

This fuctionality was merged into the `master` branch in 2021, so I assume we can safely close this issue. Please re-open it again @vtmatteo - if you disagree and feel...

The "YAML data" might be the sum of a potentially large prepended file followed by the main input file. What should then be stored in the PNG file? If storing...

@jacobian91 I like your solution to my scenario above. Splitting the prepended and main YAML into separate embedded sections will indeed make it easier to restore the original YAML files...

Any connector and cable might contain an image read from an image file. A YAML input that contains such image filenames cannot be processed without access to those image files....

All code from the `latest` branch have just recently been merged into the `dev` branch, so I encourage you to try that out. Your code example seems very close to...

Thank you for the suggested functionality. A lot of new code has just recently been merged into the `dev` branch, and I don't know yet if something similar is already...

I agree that when "-" as input file should be interpreted as STDIN, then "-" as output file similarly should be interpreted as STDOUT. The output filename stem is by...

Your arguments about the `parse` function seems reasonable and should also reduce the need for `Any` in type hints due to a cleaner API, but I am a bit worried...

What happens if any connector or cable contains an image? Where should WireViz look for image files with relative paths when the YAML input is read from STDIN? Maybe #322...