kvid

@EvilMustacheTwirl wrote: > > Since the errors don't report where in the input file the issue is [and ...] I agree that reporting "where in the input file the issue...

#186 was merged to `dev` last year, and is now included in v0.4. #251 is next in line for developing against v0.5 with some heavy refactoring of a large part...

Thank you for suggesting this new feature. I've not worked much with the parsing part of WireViz, myself, but the pyyaml library should be able to parse `---`. However, I...

@alecraymond - Thank you for this suggested feature. It would need to be an optional feature. Othewise, it would be impossible to document single connectors without any connections. However, you...

I'm sorry that I managed to close this issue by a mistake while writing my answer, and my answer was also saved before it was finished. That was not my...

@alecraymond - v0.4 was released today, and it includes new functionality that I believe resolves this issue. Please try it and report back here your findings.

As far as I know, pyyaml does not support line numbers out of the box, but it might be possible [via subclassing](https://stackoverflow.com/questions/13319067/parsing-yaml-return-with-line-number). However, an easier approach, is to specify node...

Thank you for reporting your use case. This must be a simple bug, was my first impression, and I quickly located two code locations where I added one extra indentation...

@ask6483, do you also request controlling `ignore_in_bom` for each additional component? That would enable ignoring any combination of connector/cable entry and additional component entries in the BOM. However, the same...

@scottbouch, thank you for sharing your use case. I don't know how to better accomplish your request with the current versions, but maybe a future version can support this. See...